This book is packed with practical insights you can apply right away. The explanations are clear, the examples are relevant, and the principles really help you write cleaner, more maintainable code as well as providing other team members more relevant feedback, especially in PRs. I was surprised at how many ideas I could use immediately at my work. Highly recommended for anyone who wants to level up their coding skills.

It's a very good read and worth every penny I spent. I feel I have improved a lot as a programmer in the process and have nearly halfed the time needed to write complex systems. This book is mostly aimed at professional programmers looking to become better programmer though I suppose it can still help you improve your skills if you code as a hobby. My background is that of a professional junior .NET programmer who develops video games in his spar time using Unity. Now, this book mostly uses Java for its examples but it (for the most part) translates well into other languages so it really doesn't matter where you're coming from. It won't teach you how to program so you'd best have that covered already. What it will teach you is how to become better at it.

Very good!

While I don't agree with some of the points the author raises, I do recognize it is very well written and organized. Despite being a technical book, it is an easy read and is it also applicable to real life code. Recommended for both students and seasoned professionals.

It is a good beginner book for improving coding convention. Writing software programs

Incredible book, I changed completely the way I code. Some of those knowledge you probably have, but you will find motivation and reasons about why you should implement those and much more new knowledge when coding.

The book is an excellent book for rockie or seasoned programmer. I found the author of extensive experience and excellent writing style. Off course, there are some sections in the book where the author emphasis is too much or some of his ideas sound radical but remember his opening of the book, there is no right or wrong in the discipline of clean code.

This author has a flawless way to convey his message. He writes in a way that everyone can understand and his points can easily be applied not only to the programming field but to life in general.

One of the best books on the programming. Absolutely must have. Big bonus is that the book will be very helpful bo matter what is your primary programming language.

Excelente libro

Every so often, a book comes along that codifies best practice in a way that manages to illuminate the path from where things are right now, to a better place that we'd rather be -- things like Fowler et al. Refactoring: Improving the Design of Existing Code (Object Technology Series) or the Gang of Four Design patterns : elements of reusable object-oriented software. This is one of those books. And if much of the material is the sort that seems obvious in hindsight -- well, that is the mark of a well written book, to make the concepts that clear.

Taking a series of real world examples -- open source projects with significant user bases, including FitNesse and JUnit -- a series of worked examples take us from good, or at least adequate, code, to a form which is better factored, and easier to read, with the steps along the way clearly marked. Yes, even some of Kent Beck's code is put under the microscope, and carefully polished that extra stage or two more.

The reader is cautioned that, without working long hours to follow these examples, this will be just another of those feel-good books. I don't quite agree -- spending just a little time to follow the transformations, and then reflecting on one's own outpourings should be enough to make this a feel-bad book. All the sins from obscurely named variables to sprawling functions that gaily mix abstraction levels, we've all done them (especially programming in FORTRAN on minicomputers with slow stacks and a rule of thumb that 1 call ~ 40 loc in terms of performance).

The maxim to take from the book is based on Baden-Powell's "Try and leave this world a little better than you found it", and owes to the same school of thought as "whenever you are in the garden, pull at least one weed". The meat of the book is in distinguishing what are the weeds from the intended crop.

So read it, understand the examples, and then refer to it often -- like the other titles mentioned, it is a reference work, and should join them as among the most thumbed on your bookshelf.

.

This is a great book. I have found the concepts informative and helpful. I'm glad I decided to get it. As an aid, I listened to the audio book version while I followed along reading it. This made taking notes a dream. I am now on my way to leveling up my programming skills.