If you have been working on software development for a while, it’s for sure that you already know how important this matter is, if don’t, please read right away, will save you some headaches. I think it doesn’t matter at what level of expertise you’re, this book will always help to anyone to clarify some ideas or concepts related to the coding process.

My team and I have decided to read it and share some thoughts about it in a weekly basis and would be fair to say that has been one of the most productive decisions we’ve made as a team to improve our code quality. So, I’ll be putting here some notes that we’ve considered as key during our discussions so far, but no doubt there is much great content in it, so give it a look in the preview available on Amazon and then you may want to buy it as we did:

Chapter 1: Clean Code

• As the mess builds, the productivity of the team continues to decrease, asymptotically approaching zero.

• The Boy Scout Rule: Try and leave this world a little better than you found it…

Chapter 2: Meaningful Names

• The length of a name should correspond to the size of its scope

• One difference between a smart programmer and a professional programmer is that the professional understands that clarity is king.

Chapter 3: Functions

• The first rule of functions is that they should be small. The second rule of functions is that they should be smaller than that.
• FUNCTIONS SHOULD DO ONE THING. THEY SHOULD DO IT WELL. THEY SHOULD DO IT ONLY.
• The ideal number of arguments for a function is zero (niladic). Next comes one (monadic), followed closely by two (dyadic). Three arguments (triadic) should be avoided where possible. More than three (polyadic) requires very special justification—and then shouldn’t be used anyway.
• Flag arguments are ugly. Passing a boolean into a function is a truly terrible practice.

Read still in progress, have you read it already?, share your thoughts in the comments, See you later! 🙂