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, who has helped bring agile principles from a practitioner’s point of view to tens of thousands of programmers, 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 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
- What “smells” and heuristics can help you identify bad code
This book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.
Why?
Everything is in the link.
Everything is in the link.
Not really. That blog post has a hand full of cherry-picked opinions, many of which are of dubious reasoning and substance. That’s hardly an argument to stop recommending the book.
The opinion is not “cherry-picked”, nor are the highlighted examples from the book unique or lacking context. It is a long, thoughtful and articulate criticism of multiple passages from “Clean Code”, and display a fundamental problem with the advice it gives. It’s not to pretend there’s no good advice in the book, but that the bad advice is really bad and very prominent. Also, it’s impossible to finish since the back half is Java-centric, a relic of the era it was written.
Certainly not everything in his books is bad, and not everything that is bad today was bad when it was originally written. The biggest problem with the quality of his books, is that there’s a mix of good, bad, and out-dated advice in there, and for the beginners/Juniors reading his books, it’s genuinely hard to tell the difference. I think people would be better off looking for sources that avoid some of the mistakes that he made, amd speak to a more modern audience who are working with recent technologies and in work environments as they exist today.
It’s not to pretend there’s no good advice in the book, but that the bad advice is really bad and very prominent.
Care to point out what you think is he absolute best example that supports your point?
A single example will do.
Otherwise all you have to show is an unsupported personal observation which contrasts with what’s written on the book.