Clean Code: A Handbook of Agile Software Craftsmanship 1st Edition, Kindle Edition

by Martin Robert C. (Author) Format: Kindle Edition

Part of: Robert C. Martin Series (13 Books)

Flip to back Flip to front

Audible Sample Playing... Paused You are listening to a sample of the Audible narration for this Kindle book.
Learn more

ISBN-13: 978-0132350884

ISBN-10: 0132350882

Why is ISBN important?

Share <Embed>

Other Sellers

from

Other Sellers

See all 6 versions

Buy

$28.79

eBook features:

Highlight, take notes, and search in the book
Length: 1168 pages
Enhanced Typesetting: Enabled
Page Flip: Enabled
Part of: Robert C. Martin Series (13 Books)
Due to its large file size, this book may take longer to download

Read with the free Kindle apps (available on iOS, Android, PC & Mac), Kindle E-readers and on Fire Tablet devices. See all supported devices

Sold by: Amazon.com Services LLC

Digital List Price: $39.99

Print List Price: $49.99 Save $21.20 (42%)‎

Enter a promotion code or Gift Card

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 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.

Customers who bought this item also bought

Page 1 of 1 Start overPage 1 of 1

Martin Robert C.
1,278
Kindle Edition
in Systems Architecture
$22.32
Robert C. Martin
758
Kindle Edition
$19.79
Thomas David
952
Kindle Edition
$28.79
McConnell Steve
824
Kindle Edition
$25.41
Fowler Martin
421
Kindle Edition
$32.39
Gamma Erich
1,368
Kindle Edition
$32.39

More items to explore

Page 1 of 1 Start overPage 1 of 1

Fowler Martin
421
Kindle Edition
$32.39
Gamma Erich
1,368
Kindle Edition
$32.39
Eric Freeman
57
Paperback
$41.45
McConnell Steve
824
Kindle Edition
$25.41
Sam Newman
604
Kindle Edition
$24.99
Thomas David
952
Kindle Edition
$28.79

Amazon Business: Make the most of your Amazon Business account with exclusive tools and savings. Login nowAmazon Business : For business-only pricing, quantity discounts and FREE Shipping. Register a free business account

Editorial Reviews

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 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.

--This text refers to the paperback edition.

About the Author

Robert C. “Uncle Bob” Martin has been a software professional since 1970 and an international software consultant since 1990. He is founder and president of Object Mentor, Inc., a team of experienced consultants who mentor their clients worldwide in the fields of C++, Java, C#, Ruby, OO, Design Patterns, UML, Agile Methodologies, and eXtreme programming. --This text refers to the paperback edition.

Product details

ASIN : B001GSTOAM
Publisher : Pearson; 1st edition (August 1, 2008)
Publication date : August 1, 2008
Language : English
File size : 42806 KB
Simultaneous device usage : Up to 5 simultaneous devices, per publisher limits
Text-to-Speech : Enabled
Enhanced typesetting : Enabled
X-Ray : Not Enabled
Word Wise : Not Enabled
Print length : 1168 pages
Lending : Not Enabled

Best Sellers Rank: #17,037 in Kindle Store (See Top 100 in Kindle Store)
- #3 in Software Development (Kindle Store)
- #6 in Software Testing
- #18 in Software Development (Books)

Customer Reviews:
2,895 ratings

Customer reviews

5 star		81%
4 star		10%
3 star		3%
2 star		2%
1 star		3%

How are ratings calculated?

Top reviews from the United States

There was a problem filtering reviews right now. Please try again later.

Deal Stealer

Swallowed My Pride and bought this book

Reviewed in the United States on December 30, 2016

Verified Purchase

I've been programming about 17 years and consider myself above average programmer. Yet, this book made me feel like I'm actually horrible coder. I've always gotten my tasks done but I didn't pay attention on refactoring to clean up the code. I'm already behind and got a demo coming up in few days. As I'm reading my guilty verdicts on all his 'bad code' examples, it inspire me to care about 'coding' yet again. It can be fun and it's not all about getting the job done. What's sad about the reality is that 'bad code' will continually increase over time because people don't realize what 'bad code' can do in the long run.

Every programmer regardless of experience should read this book. Thanks!

229 people found this helpful

Helpful

Jim

Good, but tightly coupled to Java and starting to age poorly

Reviewed in the United States on November 3, 2018

Verified Purchase

3.5 stars. I'm rounding up.

Much of the information in this books is eye opening, particularly the chapters on functions, classes, and code smells. However, a serious problem is that this book is very, very Java-centric, and it is clearly a product of its 2009 copyright date. Many of the chapters have been made moot (PEP8 and Prettier making the formatting chapter largely obsolete, for example), and a few aren't totally applicable to any other language.

Note about buying a new, physical version from Amazon: don't. The book will be damaged in shipping as it just comes in a padded envelope and will be dog-eared like a used book before you receive it. See my picture.

85 people found this helpful

Helpful

Mark Jones

Java & OOP centered

Reviewed in the United States on December 8, 2018

Verified Purchase

Stay far away from this book of you are not an OOP programmer. All examples are in Java but most C++ programmers should be able to mentally translate the ideas. There is also too much focus on Java specific tooling. While there are some good points this book makes, it disregards many good programming techniques used in standard imperative languages without objects. It completely disregards functional languages and given gives some terrible advice when it comes to writing good code in a functional style. Overall it's pretty good up to about chapter 7. After that it's pretty much downhill.

42 people found this helpful

Helpful

Juan M. Paulino

It's fake.

Reviewed in the United States on June 6, 2018

Verified Purchase

This books is a fake. Don't buy it. Look at the images I posted.

75 people found this helpful

Helpful

Roman

The content is good, but the soft cover version of the book ...

Reviewed in the United States on July 9, 2018

Verified Purchase

The content is good, but the soft cover version of the book is of a poor print quality, it looks like it was printed from photocopies.
I've heard that originally, the print quality was ok, well, it's not anymore.
It's still readable, but I would never buy it if I new about the print quality.
Should've read other reviews.

41 people found this helpful

Helpful

Chris

Poor quality reprint

Reviewed in the United States on May 21, 2018

Verified Purchase

Bought the book due to a push at work to read this, the book was bought through Amazon.com Services, Inc. and like others have said I received a copy with huge margins on each page, a blurry cover, and no spine or back. I didn't have any of the problems of the binding falling apart yet, the text is readable its just the code samples are a bit hard to read.

36 people found this helpful

Helpful

I've become a better and more mature developer

Reviewed in the United States on March 30, 2017

Verified Purchase

I've been reading this for the past few weeks and just by applying the principles and concepts I've learned so far, I've become a better and more mature developer. The lead dev on my team recently noticed and commented on the positive changes in my code as of late. He was also impressed when I used what I learned to refactor a bit of our code base. Even though it's Java-based and I am a Go developer with a background that is primarily JS, I've been able to use the ideas in this book to clean up my own code, both personally and professionally.

44 people found this helpful

Helpful

Terry

Instills a mindset or way of thinking about programming

Reviewed in the United States on July 9, 2017

Verified Purchase

This is a critical thinkers book. It gives the reader a basis to use within their own programming style and language of choice.

The code examples are written in Java and are there to show how to refactor code based on the principles and reasoning within the book.
This is not a book that I take as a specific do this or else, more of a guide that explains why you should consider writing code in the way described.

Essentially the lesson is to create code that is small, has a specific purpose and does that one thing.
When functions or methods begin to stray into doing multiple things spin those code pieces off on their own and repeat.

What I get from this book is a mindset or way of thinking about programming. To create code that is cohesive, is small, does not have unnecessary parts. When these principles are broken find a way to refactor or eliminate the additional pieces. It is not just about taking away or keeping code small but adopting a way of thinking about the design of the program and how each piece interacts with the other parts.

The suggested line lengths of functions mentioned and other very specific examples is more where your critical thinking comes into play. I do not program in Java so many of the language specific scenarios do not apply to me. in some languages you just can't have or do some of the things suggested. Though as a general rule of thumb I find the examples helpful and when I mean general rule of thumb I do not mean a specific line count or size but a simplistic do as little as possible to achieve the goal. Simplify. Simplify. Simplify.

I purchased and received the 16th printing of this book, published February 2016.
There are no weird formatting or printing issues with the book as others have mentioned.

If you have the ability to reason and think critically, being able to adapt examples and suggestions to your own style and language then I highly recommend this book. The contents are NOT common sense and do not come naturally to the uninitiated. The book does take you by the hand in a certain way leading you from the process of just make the program work to thinking about the logic design and function of your programs.

When you are in situations where redesign is not possible the principles learned from this book will help you to refactor when possible and write new code that is better, smaller, tighter. Making you a better more valuable programmer.

34 people found this helpful

Helpful

Top reviews from other countries

Translate all reviews to English

Sam Tuke

Fake copy, printed by Amazon, but readable

Reviewed in the United Kingdom on May 12, 2018

Verified Purchase

This is a review of the printing (physical product) not the content. It appears to be fake. The front page is highly pixellated, the back cover and spine are both white blank. The pages are too large for the content resulting in considerable whitespace around the page content. Overall the book is larger than the "real" edition, and heaver as a result. The penultimate page states "Printed in Poland by Amazon fulfillment". This book is not printed by the original publisher, Prentice Hall, therefore.

In all the book is still perfectly usable and the quality issues do not affect the paper quality or resolution of the pages themselves. The only real downsides are the ugly front cover and larger/heavier than necessary physical form. The situation regarding intellectual property is unclear.

My verdict: buy it anyway, but be aware its not the Real McCoy.

48 people found this helpful

Little Bobby Tables

I mean he calls himself Uncle Bob...

Reviewed in the United Kingdom on August 9, 2019

Verified Purchase

I have worked in both legacy code bases and green field projects over a long career. I bought this book many years ago, since I always am willing to learn, and had ample time to reflect on it. It's advice is not too bad, mostly obvious, but rather shallow and focused on the details I can quickly teach graduates, rather than the real depth I want them to think about. Still I didn't think strongly about posting a negative review until I looked at one of the author's own codebases, FitNesse. It defies so many of the author's own principles it beggers belief, but moreover is has a dreadful design for important reasons he doesn't cover. In this I am looking throughout the project's history: it's a house of cards. And that is very telling. Because here is a mediocre book from an author who rather incredibly calls himself "Uncle Bob", as if he is some friendly elder dispensing wisdom. Why do we fall for it, in a field of engineering and science? He would be better to mend his own fences before teaching others how to paint them.

27 people found this helpful

bomfirit

Gedrucktes PDF!!!

Reviewed in Germany on November 7, 2017

Verified Purchase

Das Buch sollte jeder Entwickler kennen. Pflichtlektüre! Aber, bitte nicht hier bestellen! Was man bekommt ist ein gedrucktes PDF, welches dummerweise in der falschen Papiergröße bedruckt ist. Man hat also an den Rändern riesige weiße Flächen. Das Buch ist daher unnötigerweise ca 25% größer als das Original. Zudem ist die verwendete Tinte sehr hell. Die Codebeispiele sind kaum zu lesen. Das Cover ist im Vergleich zum Original verwaschen. Das Buch geht sofort zurück und wird im Laden (zur Ansicht) bestellt. Jetzt weiß ich warum die Lieferzeit auch 3 Wochen betrug. Das Buch wird offensichtlich auf Anfrage gedruckt.

Bei den beigefügten Bildern sieht man das Original (von der Firma) und das hier bestellte Buch (PDF Druck)

166 people found this helpful

Translate review to English

Thomas

Leider eine billige Kopie, bitte nicht bestellen.

Reviewed in Germany on April 21, 2018

Verified Purchase

Meine Renzension bezieht sich ausschließlich auf das erhaltene Exemplar. Ich habe direkt bei Amazon bestellt (Verkauf & Versand durch Amazon), kein Marketplace.

Wie bereits von anderen Personen festgestellt, habe auch ich leider eine billige Kopie des Originals erhalten - vermutlich ein Druck der PDF-Version. Der Druck ist schlecht, das Format ist unnötigerweise sehr viel größer, das Cover ist verschwommen/verpixelt, kein bzw. weißer Buchrücken und -rückseite.

Hierfür über 29€ zu verlangen grenzt an Betrug. Ich habe das Exemplar unmittelbar zurückgeschickt. Schade.

63 people found this helpful

Translate review to English

randomboy93

This is a good book for beginner developers

Reviewed in the United Kingdom on February 8, 2018

Verified Purchase

This is a good book for beginner developers, or for whom who just want to review and refresh all the principles of the clean code. If you are an experienced programmer, I am sure that sometimes you will find this book obvious, and sometimes very illustrative.

Before reading this book, I recommend having a good understanding of Java and Object-Oriented programming. Don't forget Abstract classes, Interfaces, and Polymorphism.

In my opinion, it has more than 100 pages in excess.The appendixes and the chapter 14 (Refinement) don't contribute to anything. They are just boring. Also, I think that chapter 13 (Systems) could seem a little bit complex for beginners. It needs a very specific knowledge of Java, with concepts like EJB, JNDI, Proxies, and so on.

On the other hand, every concept is explained accurately with lots of examples. In addition, the "Smells and Heuristics" chapter summarizes the essence of this book very well.

15 people found this helpful

See all reviews

Customers who viewed this item also viewed

Page 1 of 1 Start overPage 1 of 1

Martin Robert C.
1,278
Kindle Edition
in Systems Architecture
$22.32
Thomas David
952
Kindle Edition
$28.79
Robert C. Martin
220
Kindle Edition
$38.47
Fowler Martin
421
Kindle Edition
$32.39
Robert C. Martin
758
Kindle Edition
$19.79
McConnell Steve
824
Kindle Edition
$25.41

What other items do customers buy after viewing this item?

Page 1 of 1 Start overPage 1 of 1

Clean Code: A Handbook of Agile Software Craftsmanship 1st Edition, Kindle Edition

Buy for others

Buying and sending eBooks to others

Customers who bought this item also bought

More items to explore

Editorial Reviews

From the Back Cover

About the Author

Product details

Customer reviews

Reviews with images

Top reviews from the United States

There was a problem filtering reviews right now. Please try again later.

Top reviews from other countries

Customers who viewed this item also viewed

What other items do customers buy after viewing this item?