Twitter | Search | |
Search Refresh
Horm Codes Dec 11
tip! How to avoid nesting? One way is checking special cases first and then returning the default value...
Reply Retweet Like
Adil Hussain Dec 6
Replying to @adil_hussain_84
: Bad code tries to do too much, it has muddled intent and ambiguity of purpose. Clean code is focused. Each function/class/module exposes a single-minded attitude that remains entirely undistracted, and polluted, by the surrounding details.
Reply Retweet Like
Kevin Dec 12
I just write down some thoughts about how Value Object makes your code more meaningful
Reply Retweet Like
Adil Hussain Dec 6
Replying to @adil_hussain_84
: Readers of our code should perceive us to have been decisive.
Reply Retweet Like
Muva Technologies Dec 12
PLUGINS: if that's all that a web designer talks about, run!!!. Here are more signs to check when hiring a designer:
Reply Retweet Like
absolutholz Dec 11
Clean Code applied to JavaScript — Part I. Before your start - DEV Community 👩‍💻👨‍💻
Reply Retweet Like
Cornelius A. Ludmann Dec 12
Great talk about in |s at the Meetup Ruhrgebiet nicely set in scene by and using four concrete cases.
Reply Retweet Like
Scala Jobs Dec 13
Do you have experience? 🛒 Are you passionate about ? 🧹 Would you like lots of and an ? 💸 This could be your chance to shine✨ DM for more information or apply through the link below👇
Reply Retweet Like
absolutholz Dec 11
Clean Code Isn't a Goal, but a Solution: How to Write Clean Code and Why It Matters - DZone Agile
Reply Retweet Like
Jaweriya Nazneen Dec 6
Clean code always 1. Looks like it was written by someone who cares. 2. Runs all the tests; 3. Contains no duplication 4. Expresses all the design ideas of the system 5. Minimizes the number of entities such as classes, methods 6.*** Human readable code ++
Reply Retweet Like
Włodek Krakowski Dec 11
Speaking at in Bulgaria. Of course about refactoring to achieve better (cleaner, more readable, testable, maintainable...) code & injecting new habits into your development processes to make it happen every day continuously.
Reply Retweet Like
Piercarlo Slavazza Dec 12
Do you know what "Double Dispatch" is and why it will help you in writing better and cleaner code? Check out my latest Medium article!
Reply Retweet Like
Dastin Kuwałek Dec 7
Coding The way at Conference hosted by Engineering Design Center
Reply Retweet Like
Enno Dec 12
Where to put closing brackets of functional calls? Option 1: in separate line at the end: oref->perfect_function( date = sy-datum ). Option 2: at the end of last statement: oref->perfect_function( date = sy-datum ). Option 3: depends on the stmt length
Reply Retweet Like
Timo Körber • Web-Consulting Dec 13
What‘s your opinion on „Clean Code“? At the „Agile Konferenz 2019“ in Frankfurt I talked about how important Clean Coding is for an efficient development and a successful project.
Reply Retweet Like
ashok athukuri 1h
Even your editorial code examples are badly written with poorly named variables. I understand its about but using s for sum !?
Reply Retweet Like
Adil Hussain Dec 13
Replying to @adil_hussain_84
advice on naming: Hunting for a good name often results in a favourable restructuring of the code.
Reply Retweet Like
Matthew MacDonald Dec 11
The most controversial point in my piece on bad programming practices was that comments aren't evil. I'm familiar with , of course, but it's insane to me to that some shops have policies *forbidding* comments. If comments are lies, then what's an API doc going to be?
Reply Retweet Like
Muva Technologies Dec 12
Reply Retweet Like
Phoebe Voong-Fadel Dec 11
My early Christmas present from “Clean Code” by Robert C. Martin Read the intro and know I’ll like it! The sign of good code is measured by the number of WTFs per minute. 😂
Reply Retweet Like