The text of this article is not in this database — only its details are. The old site it was published on is gone, but the Internet Archive kept a copy: Book Review: Clean Code - A Handbook of Agile Software Craftsmanship
Join the conversation! Your thoughts help the community grow.
Sign in to leave a comment
It is the same account you read, post and publish with — and you will come straight back to this page.

Pankaj BajajPosted Apr 23, 2014, 11:10 PM
great article.. I read that book and it's changed my way of coding..
Sam HobbsPosted Feb 8, 2013, 8:42 PM
I would call a programmer mediocre if they produce code that works when it goes into production but has many bugs when it is in production. To the extent that their code is buggy is partially the result of an inability to understand their own code, the ability to understand is relevant. In my opinon, the emphasis should be on the analysis phase, not the coding phase. The best programmers have a clean understanding of what they are doing. If they do, then their code will be easier to understand. When Structured Programming was new, many people thought that it was saying that code needs to be structured physically. That is not what it said. It said that software needs to be structured logically. Code can be structured physically to look pretty and still be spaghetti code.
Mahesh ChandPosted May 5, 2010, 11:22 PM
Great review. I plan to order this book now.
Marcio MangarPosted May 5, 2010, 3:02 PM
Clean Code is one of my top 3 books. Uncle Bob did an incredible job putting all good manners together on that book. It doesn't care the language, Assembly, C#, Java or Ruby. Great developers with great sense of responsibility do great jobs with any kind of language.