167 books
—
484 voters
Goodreads helps you keep track of books you want to read.
Start by marking “Clean Code: A Handbook of Agile Software Craftsmanship” as Want to Read:
Clean Code: A Handbook of Agile Software Craftsmanship
(Robert C. Martin Series)
by
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 . M ...more
Noted software expert Robert C. Martin presents a revolutionary paradigm with Clean Code: A Handbook of Agile Software Craftsmanship . M ...more
Get A Copy
Paperback, 464 pages
Published
August 1st 2008
by Pearson
(first published January 1st 2007)
Friend Reviews
To see what your friends thought of this book,
please sign up.
Reader Q&A
Community Reviews
Showing 1-30
Start your review of Clean Code: A Handbook of Agile Software Craftsmanship
Mar 08, 2015
Oana Sipos
is currently reading it
These are rather notes than a review while reading:
1. Use very descriptive names. Be consistent with your names.
2. A function should not do more than one thing.
3. SRP (Single Responsibility Principle): a class or module should have one, and only one, reason to change.
4. Stepdown rule: every function should be followed by those at the next level of abstraction (low, intermediate, advanced).
5. A long descriptive name is better than a short enigmatic name. A long descriptive name is better than a ...more
1. Use very descriptive names. Be consistent with your names.
2. A function should not do more than one thing.
3. SRP (Single Responsibility Principle): a class or module should have one, and only one, reason to change.
4. Stepdown rule: every function should be followed by those at the next level of abstraction (low, intermediate, advanced).
5. A long descriptive name is better than a short enigmatic name. A long descriptive name is better than a ...more
The first half of this book is well worth a read. Then I was reminded of Martin Fowler's (I think) comment that the original Design Patterns Elements of Reusable Software book was a response to the limitations of C++. It dovetailed so well into Java because Java has a lot of the same annoying limitations, and in some ways is even harder.
The latter section of the book contains some worked examples that I didn't always agree with because they seemed to be totally over done. A lot of the refactorin ...more
The latter section of the book contains some worked examples that I didn't always agree with because they seemed to be totally over done. A lot of the refactorin ...more
This book makes some very good points, sometimes taking them to extreme ("Never write functions longer than 15 lines! Never write functions with more than three arguments!"). Some of these points were quite new and useful for me - YMMV. It's too Java-specific in a few places, and reading the last refactoring chapter on a kindle was quite a challenge, but otherwise it was well worth a read. At least I got a clear picture of how I want to refactor a big piece of my current project after reading th
...more
There is a movement brewing in the world of professional software development. This movement is concerned not merely with writing functional, correct code, but also on writing good code. Taking pride in code. This movement is the Software Craftsmanship movement, and one of the people near the head of this movement is Robert C. Martin, also known as Uncle Bob.
His book "Clean Code" is, in many ways, an introduction to the concept of Software Craftsmanship and a guide for developers interested in b ...more
His book "Clean Code" is, in many ways, an introduction to the concept of Software Craftsmanship and a guide for developers interested in b ...more
I had a tough time deciding between 3 or 4 stars.
The book should be called Clean Java Code. Some of the concepts definitely translate to other languages, but it uses Java for all of the examples and some of the chapters are dedicated to Java-specific issues.
I consider many of the the suggestions to simply be common sense, but I've worked with enough of "other people's code" to realize they don't necessarily agree. With all of that said, I'd definitely recommend the book to Java developers at th ...more
The book should be called Clean Java Code. Some of the concepts definitely translate to other languages, but it uses Java for all of the examples and some of the chapters are dedicated to Java-specific issues.
I consider many of the the suggestions to simply be common sense, but I've worked with enough of "other people's code" to realize they don't necessarily agree. With all of that said, I'd definitely recommend the book to Java developers at th ...more
Many good points in this book. Unfortunately, almost all of them are overdone. Yes, you should write short functions, if possible. Yes, you should have functions that do one thing.
But no, "one thing" does not mean you should tear an algorithm apart into twenty little funclets that make no sense on their own.
Basically, like another reviewer wrote, the first part of the book raises many good points, and the second part of the book then merrily applies these points way beyond their usefulness. Read ...more
But no, "one thing" does not mean you should tear an algorithm apart into twenty little funclets that make no sense on their own.
Basically, like another reviewer wrote, the first part of the book raises many good points, and the second part of the book then merrily applies these points way beyond their usefulness. Read ...more
I was extremely underwhelmed with Clean Code! As other reviewers have noted, this book completely Java-centric and incredibly narrow in its object-oriented focus. Nowhere on the front cover, spine, or back cover is this mentioned at all.
Clean Code also relies heavily on other published works. In the case of Fowler's Refactoring and the "Gang of Four"'s Design Patterns, I wasn't too put off by it. These are pretty standard reference books and I have them on my shelf.
But the really irritating ref ...more
Clean Code also relies heavily on other published works. In the case of Fowler's Refactoring and the "Gang of Four"'s Design Patterns, I wasn't too put off by it. These are pretty standard reference books and I have them on my shelf.
But the really irritating ref ...more
Great great book on principles of clean code.
The only problem with the book was that it’s obsessively written for Java. Even though, there are still many principles you can apply to any other languages from C to Python.
Although have to say, you have to do your own research for applicability of the principle in your target language. For instance, the inversion of control (IoC)and Dependency Injection (DI) are quite common and intrinsic to Java, but it is not as straightforward in Python (becaus ...more
The only problem with the book was that it’s obsessively written for Java. Even though, there are still many principles you can apply to any other languages from C to Python.
Although have to say, you have to do your own research for applicability of the principle in your target language. For instance, the inversion of control (IoC)and Dependency Injection (DI) are quite common and intrinsic to Java, but it is not as straightforward in Python (becaus ...more
I started reading it after a lot of recommendations but it wasn't gone up to the standards.
Clean Code is about writing code which is not only understandable to the code him/herself but to the others as well.
Robert Martin mainly used a lot of JAVA code which is not applicable to other languages like Python and JAVASCRIPT. This book should not be this much lengthy and other languages must be covered so that every programmer can benefit from it.
I was looking forward to learn more about refactoring ...more
Clean Code is about writing code which is not only understandable to the code him/herself but to the others as well.
Robert Martin mainly used a lot of JAVA code which is not applicable to other languages like Python and JAVASCRIPT. This book should not be this much lengthy and other languages must be covered so that every programmer can benefit from it.
I was looking forward to learn more about refactoring ...more
This is a book that one could get started on the idea of "good code" - clean, readable, elegant, simple, easy-to-test, etc. It has the usual stuff that you'd expect - good naming convention, testable code, single responsibility, short classes, short methods - but I feel like it takes them on overdose, going to extremes (IMHO) such as setting short explicit lengths, forbidding certain constructs, and what seems like refactoring for the sake of it.
I'd actually recommend other books like the Pragma ...more
I'd actually recommend other books like the Pragma ...more
I had a tough time deciding whether I really liked or It was amazing. I liked the writing style of the book. Its simple, clean, and well crafted.
First few chapters of the book makes good practical advice from naming variables-functions-classes to writing functions to testing. Most of the smells and heuristics I found in these chapters can be found in real-world as well.
First few chapters of the book makes good practical advice from naming variables-functions-classes to writing functions to testing. Most of the smells and heuristics I found in these chapters can be found in real-world as well.
Complexity kills. It sucks the life out of developers, it makes products difficult to plan, build, and test. - Ray Ozzie, CTO, M...more
To me this book is an extension of Martin Fowler’s “Refactoring”. As a Java developer I enjoyed it. It’s an easy read. I agree with everything, except “J1: Avoid Long Import Lists by Using Wildcards” and using less of final keyword (agree with Robert Simmons here more, he explained it in his “Hardcore Java” book). This book has some useful tips on how to avoid locks and other issues in multithreaded environment (I found it very useful).
In short, it is worth reading.
In short, it is worth reading.
I hate to say this, but I wasn't as impressed with this book as I thought I should have been, given its place in the pantheon of programming books.
The first half was excellent, but the second half left me a bit cold. It was too Java-y, and had -- dare I say it -- too much code in it.
However, I still list this as a must read for all developers. ...more
The first half was excellent, but the second half left me a bit cold. It was too Java-y, and had -- dare I say it -- too much code in it.
However, I still list this as a must read for all developers. ...more
A good book to read for any coder - perhaps not as thorough as Code Complete but much more effective than Pragmatic Programmer.
This book's biggest strength is that it includes tons of code examples, including some fairly long and in depth ones. Instead of just listing rules or principles of clean code, many of the chapters go through these code examples and iteratively improve them. The rules and principles fall out of this process and the reader is a part of developing them, which is an effect ...more
This book's biggest strength is that it includes tons of code examples, including some fairly long and in depth ones. Instead of just listing rules or principles of clean code, many of the chapters go through these code examples and iteratively improve them. The rules and principles fall out of this process and the reader is a part of developing them, which is an effect ...more
I wanted to love this book, but instead I just sort of liked it. This book is a member of the extensive genre of books on how to write clean code. It sits alongside books like Code Complete by Steve McConnell[1] and many others. Where Clean Code promised to differentiate itself was in the use of three case studies -- about a third of the book -- showing Martin's code cleanup techniques in action.
However, I was disappointed by that section. As someone who codes and reviews code professionally, t ...more
However, I was disappointed by that section. As someone who codes and reviews code professionally, t ...more
This had lots of good, practical advice that spanned everything from naming to testing to concurrency. A lot of it was pretty Java centric, so I skimmed a few sections.
By far the best portions of the book were the ones where the author demonstrates -- step by step -- his process for writing code test-first, as well as refactoring.
If you get frustrated with either of the two at times, these parts of the book are *fantastic*, because you see that even someone who's been coding for 40+ years (like ...more
By far the best portions of the book were the ones where the author demonstrates -- step by step -- his process for writing code test-first, as well as refactoring.
If you get frustrated with either of the two at times, these parts of the book are *fantastic*, because you see that even someone who's been coding for 40+ years (like ...more
Uncle Bob's book was given to me by a mate at work when I first started. I was introduced to the concept of code reviews and pull requests and told to expect a lot of comments on my code reviews to start with. I was then promptly given this book to read to minimise the pain. As a developer with ten years experience, I had seen so many of the things outlined by Uncle Bob and absolutely loved his remedies to them. I am now a convert to the idea of clean code and it has definitely made me a better
...more
You can call this book as "The Book Which Every Programmer Should READ!"
THIS BOOK BASICALLY IS A LIFE CHANGING FOR EVERY PROGRAMMER!!
as you see in the title of the book, you will learn how to write CLEAN CODE, and the rules which was the most useful in me are basically:
1. Name your variables with meaningful names. it means if you read the variable name, you'll understand what it is for
SAY WHAT YOU MEAN, MEAN WHAT YOU SAY.
2. Also name your functions with name that describe their job. If it's tak ...more
THIS BOOK BASICALLY IS A LIFE CHANGING FOR EVERY PROGRAMMER!!
as you see in the title of the book, you will learn how to write CLEAN CODE, and the rules which was the most useful in me are basically:
1. Name your variables with meaningful names. it means if you read the variable name, you'll understand what it is for
SAY WHAT YOU MEAN, MEAN WHAT YOU SAY.
2. Also name your functions with name that describe their job. If it's tak ...more
Writing clean code is what you must do in order to call yourself a professional. There is no reasonable excuse for doing anything less than your best.
---
“Honesty in small things is not a small thing.”
---
In code, refactor mercilessly.
---
The French poet Paul Valery advises us that a poem is never done and bears continual rework, and to stop working on it is abandonment.
---
Learning to write clean code is hard work. It requires more than just the knowledge of principles and patterns. You must sweat ...more
---
“Honesty in small things is not a small thing.”
---
In code, refactor mercilessly.
---
The French poet Paul Valery advises us that a poem is never done and bears continual rework, and to stop working on it is abandonment.
---
Learning to write clean code is hard work. It requires more than just the knowledge of principles and patterns. You must sweat ...more
Having reignited my love of programming I have dived into learning Unity with an aim to build games. It's purely for my personal enjoyment. Clean Code is written in an accessible, relaxed and conversational style and throws light and insight on every corner of writing, maintaining and refactoring code. Using Java examples the author clearly sets out his manifesto for elegant, well structured, concise and readable code. It feels good to be coding again.
...more
This book is #1 on my list of books I'd recommend to other programmers. I don't know how else to elaborate on how important I think the ideas in this book are.
...more
It's a great book. The only reason I give it four stars instead of five is the extremely awkward use of private fields for passing data between functions in the examples.
...more
I finally finished this!
I got through most of it months ago, but had trouble picking it back up to finish it off. I'm not sure how much of that has to do with my personal interest waning versus finding the information less useful as the book went on.
The author has strong opinions but even when I disagreed on the specifics I found wisdom in his perspective. Ironically, I liked the first few chapters quite a bit even though they were fairly superficial. They focused on the structure of code, size ...more
I got through most of it months ago, but had trouble picking it back up to finish it off. I'm not sure how much of that has to do with my personal interest waning versus finding the information less useful as the book went on.
The author has strong opinions but even when I disagreed on the specifics I found wisdom in his perspective. Ironically, I liked the first few chapters quite a bit even though they were fairly superficial. They focused on the structure of code, size ...more
Great book! There's a lot of ideas, techniques, tips, and tricks and examples that help you enhance your programming skills and coding style. I didn't like a lot the SerialDate case study because there was a lot of back and forth with the Appendix. It was quite hard for me to follow the refactoring of the SerialDate class.
Overall, I enjoyed reading the book and it helped me to generate more ideas on how to refactor and write better and cleaner code. Personally, I think it's a must-read for ever ...more
Overall, I enjoyed reading the book and it helped me to generate more ideas on how to refactor and write better and cleaner code. Personally, I think it's a must-read for ever ...more
There are very useful principles in this books that would help a programmer write cleaner code, that's for sure. However, I believe some of the statements should be taken with a grain of salt. Anyways, I'm glad I read it. Though, it would have been more helpful for me if the main focus of this book were Scala or Python instead of Java.
...more
| topics | posts | views | last activity | |
|---|---|---|---|---|
| mysql training in chennai | 1 | 1 | Aug 04, 2021 01:11AM | |
| Chapter 1 | 1 | 1 | Jun 24, 2021 10:35AM | |
| Chapters 1 and 2 | 1 | 1 | Jun 24, 2021 10:34AM | |
| Goodreads Librari...: Add cover | 3 | 19 | Jun 01, 2021 04:02AM | |
| 7z Archive Password Recovery Tool | 1 | 2 | Jul 22, 2020 01:21AM | |
| How to Recover 7zip Password? | 1 | 3 | Jul 22, 2020 12:38AM |
Goodreads is hiring!
1,392 users
528 users
426 users
334 users
287 users
279 users
185 users
74 users
64 users
45 users
Robert 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 internatio ...more
He was Editor in Chief of the C++ Report from 1996 to 1999. He is a featured speaker at internatio ...more
Other books in the series
Robert C. Martin Series
(1 - 10 of 15 books)
Related Articles
It's the season of sharpened pencils, syllabi, and…maybe a few murders here and there? That's right: Dark academia is all the rage when it...
95 likes · 21 comments
No trivia or quizzes yet. Add some now »
“Truth can only be found in one place: the code.”
—
72 likes
“Indeed, the ratio of time spent reading versus writing is well over 10 to 1. We are constantly reading old code as part of the effort to write new code. ...[Therefore,] making it easy to read makes it easier to write.”
—
46 likes
More quotes…

















