Read this book, and youll learn how to *Fight software rot *Avoid the trap of duplicating knowledge *Write flexible, dynamic, and adaptable code *Avoid programming by coincidence *Bullet-proof your code with contracts, assertions, and exceptions *Capture real requirements *Test ruthlessly and effectively *Delight your users *Build teams of pragmatic programmers and *Make your developments more precise with automation. It covers topics ranging from personal responsibility and career development to architectural techniques for keeping your code flexible and easy to adapt and reuse. Ward Cunningham Straight from the programming trenches, The Pragmatic Programmer cuts through the increasing specialization and technicalities of modern software development to examine the core process-taking a requirement and producing working, maintainable code that delights its users. 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. 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. 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.
0 Comments
Leave a Reply. |