- File Size: 22400 KB
- Print Length: 884 pages
- Simultaneous Device Usage: Up to 5 simultaneous devices, per publisher limits
- Publisher: Prentice Hall; 1 edition (November 10, 2011)
- Publication Date: November 10, 2011
- Sold by: Amazon Digital Services LLC
- Language: English
- ASIN: B00666M59G
- Text-to-Speech: Enabled
- Word Wise: Not Enabled
- Lending: Not Enabled
Amazon Best Sellers Rank:
#123,799 Paid in Kindle Store (See Top 100 Paid in Kindle Store)
- #34 in Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Testing
- #70 in Kindle Store > Kindle eBooks > Computers & Technology > Programming > Software Design, Testing & Engineering > Software Development
- #285 in Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Software Development
|Digital List Price:||$56.99|
Save $14.25 (25%)
The Robert C. Martin Clean Code Collection (Collection) (Robert C. Martin Series) Kindle Edition
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.
Customers who bought this item also bought
Would you like to tell us about a lower price?
Top Customer Reviews
As an example, Martin believes that code should be clean enough not to require any comments. Personally, I like comments. If I don't have to switch context from English to a coding language, I prefer that. Having said that, Martin's point that comments can get out of date is a good one. The code can't lie, while comments can. My belief, however, is that if the developer is indeed a true "professional," he will care enough to clean up comments. Given, there is no way to mandate that, but if we are supposed to take the time to craft our code thoughtfully, certainly we can consider documentation to be a part of that.
Martin - as noted - is very passionate. I like that, up to the point where his suggestions sound like laws. Yes, we should all be professionals. Calling into question one person's professionalism because of a practice that isn't Martin's first choice doesn't help anybody, however. I felt that the books devolve into name-calling rather than always offering helpful hints. I do agree that being a professional is critical to success. I don't agree that calling people unprofessional in the hopes that they will shape up is the best way to help our profession.
The second book is filled with a bunch of anecdotes. I enjoyed them, but I'm also coming from almost 20 years in the field as well, so some of them really rang true. I'm not sure if brand-new developers will get a lot out of them. Sometimes, people need to fail to see that what they are doing isn't working.
Overall, these books were enjoyable. I'm glad that I finally read them, although I didn't learn much that I haven't already gotten from Martin's blog. It's nice to have all of that info in one place, however.
A taste of the book:
"Names should reveal intent." "The name of a variable, function or class, should answer all the big questions. It should tell you why it exists, what it does, and how it is used. If a name requires a comment then the name does not reveal intent."
"Functions Should Do One Thing. They Should Do It Well. They Should Do It Only."
"The best kind of comment is one that does not need to be written."
The most profound statement for me was "Code should be self documenting." Every piece of code I have ever written or read has always needed extensive documentation to understand it in a reasonable time. This is not saying you should not write good docs for a public API but it is saying that simply reading the variable, function, method, class, ... names should reveal what it is supposed to do and reading code once should show exactly what it does.
Following the rules the author lays out in this book pay make not only bugs easy to spot but code is clear and easy to read. Clear understandable code is very important to continued project development. Once the core code for a program is written almost 10 times as much time is spent reading what already exists verses writing new code, so the easier it is to understand the old code the faster you can add new code.
If you want to become a better developer this book is for you.
*I'm an embedded C developer by day (No C++ compilers for the parts I work with or I'd be an embedded C++ developer), so I skipped over the chapter on JUnit.
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.
Most Recent Customer Reviews
Set up an Amazon Giveaway
What other items do customers buy after viewing this item?
Look for similar items by category
- Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Software Development
- Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Testing
- Kindle Store > Kindle eBooks > Computers & Technology > Programming > Software Design, Testing & Engineering > Software Development