Clean Code

Hi again. It’s time for a book review! Let’s start with a question for you first. Have you ever fallen victim to your own code that is several years old and now you have no idea what that piece of code even does and even fever ideas on how to fix it? I sure have, and this is the reason I chose to read a book called “Clean Code: A Handbook of Agile Software Craftsmanship” and to really see how I’ve improved during the years that I have been programming.

This book teaches us the difference between good and bad code and explains how we can write good code. Reading this book, you realize (if you haven’t already) that writing clean code is not only about writing code that works, but it’s about writing code that is easy to read even for an outsider.

The most interesting part about this book was the section where the author even asked several well-known programmers about what they think clean code is. It’s interesting because asking several people brings many views to the table and their opinions actually differed a little. But the main points I gathered while reading this book were that clean code should be easy to read, edit and understand. There were a few functional bits too like clean code shouldn’t contain duplication and it should run all tests etc. Even though I’ve been programming for years and have a pretty good idea of what clean code should look like, it actually surprised me once again how much there is to it!

I really liked this book and I agree with pretty much everything it contained, and I recommend this book to everyone who wants to write clean code. So that should be pretty much everyone in this course. Go ahead and read it!

Until next time!