- Series: Robert C. Martin Series
- Paperback: 256 pages
- Publisher: Prentice Hall; 1 edition (May 23, 2011)
- Language: English
- ISBN-10: 0137081073
- ISBN-13: 978-0137081073
- Product Dimensions: 6.9 x 0.8 x 8.9 inches
- Shipping Weight: 14.9 ounces (View shipping rates and policies)
- Average Customer Review: 134 customer reviews
- Amazon Best Sellers Rank: #16,917 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
The Clean Coder: A Code of Conduct for Professional Programmers 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
See the Best Books of 2017
Looking for something great to read? Browse our editors' picks for the best books of the year in fiction, nonfiction, mysteries, children's books, and much more.
Frequently bought together
Customers who bought this item also bought
“‘Uncle Bob’ Martin definitely raises the bar with his latest book. He explains his expectation for a professional programmer on management interactions, time management, pressure, on collaboration, and on the choice of tools to use. Beyond TDD and ATDD, Martin explains what every programmer who considers him- or herself a professional not only needs to know, but also needs to follow in order to make the young profession of software development grow.”
Senior Software Developer
“Some technical books inspire and teach; some delight and amuse. Rarely does a technical book do all four of these things. Robert Martin’s always have for me and The Clean Coder is no exception. Read, learn, and live the lessons in this book and you can accurately call yourself a software professional.”
Senior Program Manager
“If a computer science degree had ‘required reading for after you graduate,’ this would be it. In the real world, your bad code doesn’t vanish when the semester’s over, you don’t get an A for marathon coding the night before an assignment’s due, and, worst of all, you have to deal with people. So, coding gurus are not necessarily professionals. The Clean Coder describes the journey to professionalism . . . and it does a remarkably entertaining job of it.”
University of Illinois at Urbana-Champaign
“The Clean Coder is much more than a set of rules or guidelines. It contains hard-earned wisdom and knowledge that is normally obtained through many years of trial and error or by working as an apprentice to a master craftsman. If you call yourself a software professional, you need this book.”
–R. L. Bogetti
Lead System Designer
From the Back Cover
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 codeHow to write good code and how to transform bad code into good codeHow to create good names, good functions, good objects, and good classesHow to format code for maximum readabilityHow to implement complete error handling without obscuring code logicHow to unit test and practice test-driven developmentThis book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.
Author interviews, book reviews, editors picks, and more. Read it now
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
I like the philosophy behind being a software professional, like the analogy that compares a programmer to a musician in practicing skills, and all other details for a professional.
It is easy to read, I like the writing style.
The worst part of this book is preface. I don't know how this preface made it to the book, but it is saying that developers are not professionals because it's hard for them to stick to their promises and release dates. To me preface was something like making fun of developers and that's why i have found it offensive...
I don't agree that professional developer should spare 8 hours/day working for his employer and then another 3 hours on his own study. If it should be so, the professional must be paid accordingly. I have not found anything about the other side of being professional - salary, payments... If it is your job to be responsible for every fault in the code and as book says you should pay if your fault makes an financial loss to your client, then you should also ask for adequate salary (which will cover your possible expenses for your failure).
Anyway, fantastic book which i would recommend to anyone who want to get better at his job.
I don't agree with everything he has to say. He has a lot of anecdotal reasons why he does X or Y, some of which are quite personal, but very readable, and useful in at least generating discussion even when you don't agree.
Most recent customer reviews
Uncle Bob's brilliantly combined his technical and soft skills recommendations in this...Read more