Clean Code A Handbook of Agile Software Craftsmanship
Clean Code: A Handbook of Agile Software Craftsmanship by Robert C. Martin, published by Pearson Education in 2009, is a comprehensive guide aimed at improving coding practices. This edition spans 431 pages and is presented in English. The book addresses the critical issue of poorly written code, which can significantly hinder development organizations. Martin, along with his colleagues from Object Mentor, introduces a paradigm focused on the principles and practices of writing clean code, emphasizing the importance of craftsmanship in programming.
Readers will engage with a variety of code examples, analyzing both good and bad practices. The book is structured into three parts: the first outlines essential principles and patterns, the second presents case studies that challenge readers to clean up problematic code, and the third offers heuristics and “smells” identified during the case studies. Through this process, readers will learn how to create effective names, functions, and classes, as well as how to implement error handling and unit testing. Clean Code serves as a valuable resource for developers, software engineers, and project managers seeking to enhance their coding skills and commitment to quality.
Official synopsis Publisher
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.
Author
Publisher
Topics
FAQ
What is “Clean Code A Handbook of Agile Software Craftsmanship” about?
Who is the author of “Clean Code A Handbook of Agile Software Craftsmanship”?
When was “Clean Code A Handbook of Agile Software Craftsmanship” published?
What is the ISBN for “Clean Code A Handbook of Agile Software Craftsmanship”?
What are the book details (language, pages, edition)?
