Even bad code can function. But if code isn’t clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn’t have to be that way.
Noted software expert Robert C. Martin presents a revolutionary paradigm with Clean Code: A Handbook of Agile Software Craftsmanship. Martin has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code “on the fly” into a book that will instill within you the values of a software craftsman and make you a better programmer–but only if you work at it.
What kind of work will you be doing? You’ll be reading code–lots of code. And you will be challenged to think about what’s right about that code, and what’s wrong with it. More importantly, you will be challenged to reassess your professional values and your commitment to your craft.
Clean Code is divided into three parts. The first describes the principles, patterns, and practices of writing clean code. The second part consists of several case studies of increasing complexity. Each case study is an exercise in cleaning up code–of transforming a code base that has some problems into one that is sound and efficient. The third part is the payoff: a single chapter containing a list of heuristics and “smells” gathered while creating the case studies. The result is a knowledge base that describes the way we think when we write, read, and clean code.
Readers will come away from this book understanding How to tell the difference between good and bad code How to write good code and how to transform bad code into good code How to create good names, good functions, good objects, and good classes How to format code for maximum readability How to implement complete error handling without obscuring code logic How to unit test and practice test-driven development This book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.
Code is hard to read
I’m about a quarter of the way through and the knowledge seems sound but the book totes how much code you will read through. The problem is all the code is in black. There is no syntax highlighting to differentiate anything. A real oversight, it makes it especially hard to read as someone who doesn’t know Java.
An Excellent Read for a Programmer looking to improve.
Putting aside the ebook formatting and price. I have to say this sits top shelf for me as a book that will always be a milestone in my knowledge base. Uncle Bob is quite the character and the way the writers convey the topics makes it very clear on how to take the concepts and apply them.
This is not as well structured as the old Object Oriented Design Patterns book but the appendix with the guidelines and with the application of the SOLID Principles, I would be hard pressed not to admit that my paradigm on how to code has changed!
I recommend this book for those who love code design and architecture and want to take a breach from language spec manuals and learn about the art of programming.
Downsides. The price and formatting along with the occasional beating of a point.
Good Content, Horrible Typesetting
The code is not in a fixed width font. Why in the world would a book all about reading and writing code not use a fixed width font. I can barely read the code.