Clean Code, A Handbook of Agile Software Craftsmanship
Sep 2, 2018 · 1 min read

As a recommendation I recently read “Clean Code, A Handbook of Agile Software Craftsmanship”. My global impression of the book is, it’s worth reading if you wish to hone your programming skills, but it’s too Java oriented. Still some Java concepts can be used in other programming languages.
Here is a list of notes I took from the book:
- Always use very descriptive names and be consistent with them. You’ll never know who will work later on your code, or even if you’re working on it, will you remember all the lazy names you used previously. Using a long descriptive name is way better than using long descriptive comments.
- The function should do one thing and one thing only. That’s why it’s called a function.
- Functions should at most take up to 3 arguments. Anything more than 3 isn’t good practice.
Writing clean code is what makes you professional developer.
Even though the book is Java oriented it sets a lot of principles every entry/junior programmer should follow to hone his programming skills.
