Last month, I reviewed a book about design pattern (Book Review : Design Patterns for Dummies). This month, I have read a book about making readable code titled The Art of Readable Code. The book is not about, art obviously. I read this book because I would have resigned from my current job by the time I publish this post. So, I think to leave the team without the less ambiguous code that hard to understand from anyone that replace me in the future.
I hope this review is useful for anyone especially programmer and computer science students before reading the book and understand the big picture of content inside the book what really is about. Let’s start with how the author explains the content.
How the book deliver the content?
The book has a good way to deliver an idea to the reader. Using simple English language that makes beginner programmer understanding very easily, even for a programmer with some simple basic English.
When explaining an idea, the book has a good example to show to the reader. This example is very simple and basic. While the example is long enough, the author breaks it down into separate parts that are easy to understand.
Not all about comment. All about code
Some programmers think that the best readable code is about writing a comment. So there are some that write comments for entire code or class (if in OOP). This book encourages fewer comments and also encourages making a good name for variable and structuring codes.
The book is suitable for all level programmers, range from beginner to even pro, especially when working in a team. Reading this book makes you understand how and why you should make good and readable codes for your projects.
I really encourage you to read this book before you decide to leave your team for some legit reason or even before you begin your projects.
What do you think about this book?