A good and extremely readable book on software craftsmanship. Even though non-Java programmers will find many useful guidelines. Drags a bit during case studies.

Excellent first half

The second time I read this book. The most important thing I learned again was that code doesn't have to suck. It can be clear and readable and it is totally in the hand of every developer whether he/she want's to create good or bad code. Having a pushy manager is no excuse at all.

There are some good tidbits in there. Nothing earth-shattering, and nothing new (if you spend some time looking around for things like this). Now, had I read this 'way back when', I suspect I would have enjoyed much more.

Very helpful and informative.
Unfortunately, some sections are for java issues :)

A lot of stuff is repeating the same concepts from the Pragmatic Programmer and Head First Design Patterns. However, it's still worth a read:)

There's a reason this is considered a classic. Most of the "rules" and heuristics will be familiar to any programmer, but they're rules for a reason, and when you read the examples and explanations, you will undoubtedly think of something in your code base that should be refactored. There's a few chunks of Java-specific advice in the book that I could have done without, but easy enough to skim/skip. The best parts of this book are the ones where Martin successively refactors code samples and makes incremental improvements that eventually become Clean Code. "Refactoring is a lot like solving a Rubik's cube. There are lots of little steps required to achieve a large goal. Each step enables the next."