How to write good code and how to transform bad code into good code How to tell the difference between good and bad code Readers will come away from this book understanding The result is a knowledge base that describes the way we think when we write, read, and clean code. The third part is the payoff: a single chapter containing a list of heuristics and “smells” gathered while creating the case studies. 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 second part consists of several case studies of increasing complexity. The first describes the principles, patterns, and practices of writing clean code. More importantly, you will be challenged to reassess your professional values and your commitment to your craft.Ĭlean Code is divided into three parts. And you will be challenged to think about what’s right about that code, and what’s wrong with it. What kind of work will you be doing? You’ll be reading code-lots of code. 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. Martin presents a revolutionary paradigm with Clean Code: A Handbook of Agile Software Craftsmanship. Live Courses: See upcoming live courses by Uncle Bob

Video: Clean Code Fundamentals (Clean Coders Video Series)īooks: Clean Coder, Clean Architecture, Clean Agile, Clean Craftsmanship

Every year, countless hours and significant resources are lost because of poorly written code. But if code isn’t clean, it can bring a development organization to its knees.

Clean coder