What do you think?
Rate this book
The Robert C. Martin Clean Code Collection
The Robert C. Martin Clean Code Collection consists of two bestselling A Handbook of Agile Software Craftmanship The Clean A Code of Conduct for Professional Programmers In Clean Code, legendary software expert Robert C. 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. You will be challenged to think about what's right about that code and what's wrong with it. More important, you will be challenged to reassess your professional values and your commitment to your craft. In The Clean Coder, Martin introduces the disciplines, techniques, tools, and practices of true software craftsmanship. This book is packed with practical advice--about everything from estimating and coding to refactoring and testing. It covers much more than It is about attitude. Martin shows how to approach software development with honor, self-respect, and pride; work well and work clean; communicate and estimate faithfully; face difficult decisions with clarity and honesty; and understand that deep knowledge comes with a responsibility to act. Readers of this collection will come away understandingHow 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 it means to behave as a true software craftsman How to deal with conflict, tight schedules, and unreasonable managers How to get into the flow of coding and get past writer's block How to handle unrelenting pressure and avoid burnout How to combine enduring attitudes with new development paradigms How to manage your time and avoid blind alleys, marshes, bogs, and swamps How to foster environments where programmers and teams can thrive When to say "No"--and how to say it When to say "Yes"--and what yes really means
699 pages, Kindle Edition
First published November 10, 2011
About the author
Robert C. Martin
49 books1,832 followersRobert Cecil Martin, commonly called Uncle Bob, is a software engineer, advocate of Agile development methods, and President of Object Mentor Inc. Martin and his team of software consultants use Object-Oriented Design, Patterns, UML, Agile Methodologies, and eXtreme Programming with worldwide clients.
He was Editor in Chief of the C++ Report from 1996 to 1999. He is a featured speaker at international conferences and trade shows.
He was Editor in Chief of the C++ Report from 1996 to 1999. He is a featured speaker at international conferences and trade shows.
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 25 of 25 reviews
June 16, 2013
Two great books, in one nice ebook. Both books are highly recommended for any developers who are serious about their craft. I would also recommend "The Clean Coder" for anyone working with developers, and who wants to understand more about how developers (should) think and behave.
January 11, 2021
Debería leerla cualquier persona dedicada al desarrollo de software.
November 4, 2019
While the book occasionally brings up some good points, overall I felt it was full of things that have been rehashed to death in the programming community and that are largely opinion-based. I wanted to learn techniques and coding styles, not be told that it's a professional duty to have 100% test coverage, which is a highly controversial stance that isn't given any real backing in the book either!
The chapters on soft skills are probably the best and everyone should read those, just to make sure they're aware of the huge pitfalls one can have as a software developer that works in a team. But the technical chapters ranged from "okay that's good to know" to desperately trying to read faster to get away.
For example, it's not obvious why keeping argument count in functions is so critical that lead proliferation of data transfer objects is so preferable. It's not obvious why Command Query Separation should be respected whenever possible as opposed to considered as one possible guideline - it's in fact violated by many decent libraries. It's not obvious why the preferred style should be that methods mutate their objects instead of returning values. Overall the book ends up feeling as the opinions of one person on how OOP should be done without sufficient justification for the various suggestions and without sufficient explanation of the inherent trade-offs and tensions between the disparate guidelines.
Additionally, some chapters are made almost completely redundant by earlier chapters - a side effect of including two very similar books in the same collection.
These books might have been good reads in the mid 00s, but today they feel like things I've read from blog articles repeatedly.
The chapters on soft skills are probably the best and everyone should read those, just to make sure they're aware of the huge pitfalls one can have as a software developer that works in a team. But the technical chapters ranged from "okay that's good to know" to desperately trying to read faster to get away.
For example, it's not obvious why keeping argument count in functions is so critical that lead proliferation of data transfer objects is so preferable. It's not obvious why Command Query Separation should be respected whenever possible as opposed to considered as one possible guideline - it's in fact violated by many decent libraries. It's not obvious why the preferred style should be that methods mutate their objects instead of returning values. Overall the book ends up feeling as the opinions of one person on how OOP should be done without sufficient justification for the various suggestions and without sufficient explanation of the inherent trade-offs and tensions between the disparate guidelines.
Additionally, some chapters are made almost completely redundant by earlier chapters - a side effect of including two very similar books in the same collection.
These books might have been good reads in the mid 00s, but today they feel like things I've read from blog articles repeatedly.
November 25, 2018
Grain of salt
There are some timeless truths in this book and I’d recommend it to all aspiring software developers as core reading. That said in an attempt to provide practical advice the specifics have not stood the test of time. So I recommend reading it. I also recommend reading it in a way that you think more about the take away message than the specific words on the page. I can see why it is a classic though.
There are some timeless truths in this book and I’d recommend it to all aspiring software developers as core reading. That said in an attempt to provide practical advice the specifics have not stood the test of time. So I recommend reading it. I also recommend reading it in a way that you think more about the take away message than the specific words on the page. I can see why it is a classic though.
October 8, 2018
Definitely a must to read for any programmer. While some ideas and methods might not be right for everyone, it does provide an insight to how we might better manage our time, code and professional output. At the very least you'll see how other pros take to the field, and at worst you'll learn you've been doing it wrong and how to fix your process and mentality
August 11, 2021
Lo so, per un libro tecnico così specifico per professionisti del settore informatico, non si dovrebbe includerlo nei best.. Ma questa è una vera pietra miliare che esprime perfettamente quanto faticosamente io stesso ho appreso oltre 20 anni di lavoro.
June 22, 2017
Every developer should read these books!
February 9, 2018
Very important books for coding.
August 12, 2019
This approach resonates with me well, so recommend everyone doing software development professionally.
September 18, 2019
It's great. I'd recommend it to every programmer regardless of his experience. At first I was a bit skeptical about the Clean Coder, but after all I liked it even more than the Clean Code.
May 7, 2020
Required reading!
August 5, 2020
If you have an IT role where developing belongs to one of your tasks, you should read these books
November 17, 2020
Excellent book to help you get a better idea of how to clean up your codebase. Also makes a great case for why we are professionals and how we can go about showing others that we are.
January 26, 2022
Must read for all programmers. Though, most examples are java based and some of the points are opinionated but every programmer will gain something after reading it.
July 27, 2022
Very good explanations for Software Paradigms, classes, dependencies in the software systems and at all how to be and act like a professional software developer. I learned a lot from this book.
October 3, 2022
It's a must for any serious software architect even tough it's a little biased on how Java or C# works and sometimes takes it's advice too far
Want to read
June 29, 2024compsci is killing me slowly so this is needed
October 7, 2021
First one "Clean Code" shows age. But, second one "The Clean Coder" is gold.
Uncle Bob is an opinioned man, and that shows in his books.
First book, "Celan Code" shows age. It has several good suggestions, but several of them are either already ironed out by tools and developer culture. But certainly a good book for someone starting programming career.
Second book is gem. It defines what a "Professional" Developer mean. What kind of mindset and attitude needed to be one. Defines "Craftsmanship". Awesome book for any age group.
If anyone prefer to buy just one book out of these two books from Uncle Bob then go for second one, "The Clean Coder", though both are good.
Uncle Bob is an opinioned man, and that shows in his books.
First book, "Celan Code" shows age. It has several good suggestions, but several of them are either already ironed out by tools and developer culture. But certainly a good book for someone starting programming career.
Second book is gem. It defines what a "Professional" Developer mean. What kind of mindset and attitude needed to be one. Defines "Craftsmanship". Awesome book for any age group.
If anyone prefer to buy just one book out of these two books from Uncle Bob then go for second one, "The Clean Coder", though both are good.
January 16, 2023
This book is a must read book for any software engineer, backend preferable. In the first book you will learn the most important rules in the software development SOLID, after learning and trying to apply them your code and work quality will increase greatly. The second book is amazing because author share a lot of experience from his life and give you insight into life of a developer, and what mean to be one, this is great since there is a lack of guidance for developers, he explains that in the book as well. This is a brain candy of a book.
October 23, 2013
Very complete and thorough, this is definitely a pair of books I would recommend any IT worker (whether on the hands on or management level) to read as it provides not only practical usable insight but also organizational enlightenment.
January 8, 2017
Very good
Very clear explanation and concise.
In later chapters when the author tells stories about his working experience can be a bit boring but it's still really helpful.
Recommended for anyone who wants to take programming professionally.
Very clear explanation and concise.
In later chapters when the author tells stories about his working experience can be a bit boring but it's still really helpful.
Recommended for anyone who wants to take programming professionally.
Read
July 7, 2014After hearing uncle Bob in a few podcasts, I decided to read his book. I confess that I am not that sold for JAVA. The case study in the book takes too much time to read.
February 12, 2016
It's book have good ideas, but some ideas is bad.
February 2, 2015
The best books I ever read! Verry easy to read! Have a lot of sarcasm!
December 23, 2020
Should be read as historical lore not as golden rules. With that taken into account these are two quite readable books that will contain some good pointers on how to level up your craft.
Displaying 1 - 25 of 25 reviews