Clean Code, A Handbook of Agile Software Craftsmanship

Nikola Pavlović
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:

  1. 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.
  2. The function should do one thing and one thing only. That’s why it’s called a function.
  3. 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.

Nikola Pavlović

Written by

I am Junior Developer, my favourite topics are Software Development, Cyber security and all around tech stuff.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade