This is an excellent book to learn the theory of how to create and maintain good code, and by “good” I mean code that you (and others) understand without much suffering.

I don’t believe that by reading this you will automatically start applying it’s suggestions / guidelines, but it is a good starting point to know that part of what you’re doing now could be done in a better way.

I’ve learned most of its contents before, while working with outstanding developers — by pairing with them or maintaining code they had created before. But it was good to read a text that was formally explaining what I was doing with my code without knowing there were explanations for that way of coding.

The text on this book is clear and full of examples, making the journey much easier to understand. The chapters that I particularly didn’t like were written by other authors — they were not as clear as the text written by Uncle Bob, or their content was too specific or far away from general orientations about code organization. Maybe other people might like them, but for me they did not add much to the book.

If you don’t have much experience on developing, this is a good read for learning about how to create good code; if you’re an experienced developer, this book might explain things you’re already doing and give you formal concepts to suggest to other devs when you need to help them improve their code.

A great reading anyway.