Amazon Prime Free Trial
FREE Delivery is available to Prime members. To join, select "Try Amazon Prime and start saving today with FREE Delivery" below the Add to Cart button and confirm your Prime free trial.
Amazon Prime members enjoy:- Cardmembers earn 5% Back at Amazon.com with a Prime Credit Card.
- Unlimited FREE Prime delivery
- Streaming of thousands of movies and TV shows with limited ads on Prime Video.
- A Kindle book to borrow for free each month - with no due dates
- Listen to over 2 million songs and hundreds of playlists
Important: Your credit card will NOT be charged when you start your free trial or if you cancel during the trial period. If you're happy with Amazon Prime, do nothing. At the end of the free trial, your membership will automatically upgrade to a monthly membership.
-17% $49.99$49.99
Ships from: Amazon.com Sold by: Amazon.com
$19.98$19.98
FREE delivery January 17 - 23
Ships from: Bahamut Media Sold by: Bahamut Media
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required.
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
Audible sample
Follow the authors
OK
Clean Code: A Handbook of Agile Software Craftsmanship 1st Edition
Purchase options and add-ons
Noted software expert Robert C. Martin, presents a revolutionary paradigm with Clean Code: A Handbook of Agile Software Craftsmanship. Martin, who has helped bring agile principles from a practitioner’s point of view to tens of thousands of programmers, 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 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 Codeis 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
- What “smells” and heuristics can help you identify bad code
- ISBN-109780132350884
- ISBN-13978-0132350884
- Edition1st
- PublisherPearson
- Publication dateAugust 1, 2008
- LanguageEnglish
- Dimensions6.8 x 0.9 x 9 inches
- Print length464 pages
Frequently bought together
More items to explore
- Functions should either do something or answer something, but not both.Highlighted by 3,369 Kindle readers
- The proper use of comments is to compensate for our failure to express ourself in code.Highlighted by 3,010 Kindle readers
- FUNCTIONS SHOULD DO ONE THING. THEY SHOULD DO IT WELL. THEY SHOULD DO IT ONLY.Highlighted by 2,641 Kindle readers
From the brand
From the Publisher
From the Preface of "Clean Architecture"
“…The rules of software architecture are the rules of ordering and assembling the building blocks of programs. And since those building blocks are universal and haven’t changed, the rules for ordering them are likewise universal and changeless.
But one thing has changed: Back then, we didn’t know what the rules were. Consequently, we broke them, over and over again. Now, with half a century of experience behind us, we have a grasp of those rules.
And it is those rules—those timeless, changeless, rules—that this book is all about.”
— Robert C. "Uncle Bob" Martin
Clean Code: A Handbook of Agile Software Craftsmanship | The Clean Code: Practical Advices for the Professional Programmer | Clean Craftsmanship: Desciplines, Standards, and Ethics | Clean Agile: Back to Basics | Clean Architecture: A Craftsman's Guide to Software Structure and Design | |
Customer Reviews |
4.7 out of 5 stars
6,393
|
4.6 out of 5 stars
2,195
|
4.5 out of 5 stars
183
|
4.7 out of 5 stars
592
|
4.6 out of 5 stars
3,687
|
Price | $49.99$49.99 | $38.74$38.74 | $38.35$38.35 | $35.16$35.16 | $37.39$37.39 |
Best agile practices of cleaning code “on the fly” Software Craftsmanship. | Endure and succeed amidst swirling uncertainty and nonstop pressure. | Picks up where Clean Code leaves off, outlining additional ways to write quality and trusted code you can be proud of every day. | A clear and concise guide to basic Agile values and principles. Perfect for those new to Agile methods and long-time developers who want to simplify approaches for the better. | Direct, no-nonsense answers to key architecture and design questions. | |
"It is the best pragmatic application of Lean principles to software I have ever seen in print." —James O. Coplien, Founder of the Pasteur Organizational Patterns project | “Some technical books inspire and teach; some delight and amuse. Rarely does a technical book do all four of these things.” — George Bullock | ". . . [A] timely and humble reminder of the ever-increasing complexity of our programmatic world and how we owe it to the legacy of humankind--and to ourselves--to practice ethical development.” — Stacia Heimgartner Viscardi, CST & Agile Mentor | “What is in the world of Agile development is nothing compared to what could be. This book is Bob’s perspective on what to focus on to get to that ‘what could be.’ And he’s been there, so it’s worth listening.” — Kent Beck | "A good architecture comes from understanding it more as a journey than as a destination, more as an ongoing process of enquiry than as a frozen artifact." — Kevlin Henney |
Pick Up Where Clean Code Leaves Off
"As software developers, we have to continually solve important problems for our employers, customers, colleagues, and future selves. Getting the app to work, though difficult, is not enough, it does not make you a craftsman. With an app working, you have passed the app-titude test. You may have the aptitude to be a craftsman, but there is more to master. In these pages, Bob expresses clearly the techniques and responsibilities to go beyond the app-titude test and shows the way of the serious software craftsman."
— James Grenning, author of Test-Driven Development for Embedded C and Agile Manifesto co-author
Editorial Reviews
From the Back Cover
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
About the Author
Product details
- ASIN : 0132350882
- Publisher : Pearson; 1st edition (August 1, 2008)
- Language : English
- Paperback : 464 pages
- ISBN-10 : 9780132350884
- ISBN-13 : 978-0132350884
- Item Weight : 1.77 pounds
- Dimensions : 6.8 x 0.9 x 9 inches
- Best Sellers Rank: #14,394 in Books (See Top 100 in Books)
- #2 in Software Design & Engineering
- #4 in Software Testing
- #8 in Software Development (Books)
- Customer Reviews:
About the authors
I run the engineering organization in IBM Research that is building "accelerated science" and digital health services. Previously, I developed Scala software at Lightbend and Domino Data Lab, and I helped spread the word about Ray at Anyscale. Besides Scala, my expertise includes MLOps, data systems, and the full software development lifecycle. I am also the author of several books:
-- "Programming Scala, Third Edition", a practical book for experienced software developers that introduces this important, modern programming language.
-- "Programming Hive", a comprehensive guide to Hive, the SQL tool for Hadoop (coauthors: Ed Capriolo and Jason Rutherglen).
-- "Functional Programming for Java Developers", a succinct introduction for Java developers to the concepts of functional programming, where I motivate its importance and demonstrate how to use FP concepts in Java programs.
-- I contributed to Robert Martin's classic, "Clean Code: A Handbook of Agile Software Craftsmanship"
You can find out more about me at these web sites:
-- http://deanwampler.com: My personal home page.
-- http://polyglotprogramming.com: Presentations, white papers, etc.
-- https://deanwampler.medium.com: My blog.
-- https://linkedin.com/in/deanwampler: Career
Social:
-- https://twitter.com/deanwampler
-- https://discuss.systems/@deanwampler
-- https://post.news/@deanwampler
My main hobby, photography:
-- https://www.flickr.com/photos/deanwampler/
-- https://glass.photo/bucktrends
-- https://vero.co/bucktrends
Robert Cecil Martin (colloquially known as Uncle Bob) is an American software engineer and author. He is a co-author of the Agile Manifesto.
Bio from Wikipedia, the free encyclopedeia. Photo by Tim-bezhashvyly (Own work) [CC BY-SA 4.0 (http://creativecommons.org/licenses/by-sa/4.0)], via Wikimedia Commons.
Customer reviews
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
Learn more how customers reviews work on AmazonCustomers say
Customers find the book easy to understand and useful for coding. They appreciate the collection of best practices and principles for writing clean, organized code. The book provides good value for money and is considered a good refresher. Readers mention that the advice on unit testing, threaded code, and boundry conditions is helpful.
AI-generated from the text of customer reviews
Customers find the book easy to read and understand. It provides good guidance on SOLID principles and practices, including strategies, tactics, and idioms for using them effectively. Readers appreciate the clear and concise writing style, saying it's a terrific starting point for producing clean code.
"...developer takes charge of their own education and is constantly improving their skillset, an aspect that Martin covers in The Clean Coder...." Read more
"...The relevance of this book is enormous. Not just the programmers should read it, the education providers should also read it...." Read more
"...The last section of the book is of particular relevance as a starting point for identifying weaknesses or deficiencies in code...." Read more
"This is a critical thinkers book. It gives the reader a basis to use within their own programming style and language of choice...." Read more
Customers find the book provides a good collection of best coding practices and guidelines for writing clean code. They appreciate the clear explanations of principles and concepts at a high level, as well as detailed examples from well-known open source code. The book discusses strategies, tactics, and idioms for using the language.
"...With everyone on the team doing this, the code improves over time and everyone feels responsible for the code whether they wrote it personally or not..." Read more
"...We also learn designs, patterns, good coding practices, and many more. We don't usually spend time to learn how to write a good, readable code...." Read more
"...of Object Oriented Analysis and Design with Applications: "Clean code is simple and direct. Clean code reads like well-written prose...." Read more
"...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..." Read more
Customers find the book provides good value for money. They say the conventions chapter alone is worth the price, teaching them to write code that costs less to maintain without costing more to write. However, some readers feel the information is average and better elsewhere.
"...I own both the electronic and the hardcover version, and it was money very well spent." Read more
"...then "Clean Code" is probably worth a skim, but it is by no means the book I had hoped it would be." Read more
"...It is definitely worth it. As the book states, it will take sweat to learn to write clean code. This wasn't taught when I went to college...." Read more
"...more money from consulting work or publication, but is disingenuous for practical use." Read more
Customers find the book helpful for writing and refactoring clean code. They appreciate the author's explanation of why keeping code clean is important, and the practical advice on cleaning up code, keeping it simple, and testing it thoroughly. The book covers topics like unit testing, keeping tests simple, and cleaning bad legacy code. Readers appreciate the author's straightforward writing style and mention that the book provides a fantastic tour through basic code hygiene best practices, including reducing duplicate code and combating code rot.
"...up a large function into smaller functions, or cleaning up a conditional for improved clarity...." Read more
"...describes advice from Kent Beck: run all tests, refactoring, no duplication, express intents of the programmer and minize the number of classes and..." Read more
"...I also like how the authors walk you through the exercise of cleaning bad legacy code...." Read more
"...concise methods, it really helps make the code more readable and cleaner...." Read more
Customers find the book helpful for catching up on things they had forgotten or just hadn't thought about since previous learning. They say it helps them understand OOP better and is a great motivational read. The presentation keeps readers engaged and helps them clear their minds.
"This is a critical thinkers book. It gives the reader a basis to use within their own programming style and language of choice...." Read more
"...But even if that is the case it is still a good refresher course...." Read more
"...I'm rounding up. Much of the information in this books is eye opening, particularly the chapters on functions, classes, and code smells...." Read more
"...By the way, at the same time this can be a good complement to "Refactoring" book, maybe it doesn't bring to too more new information...." Read more
Customers find the book helpful for unit testing, threaded code, and boundary conditions. They appreciate the advice on TDD, keeping tests clean, and writing readable, testable code. The book provides great information and helps them understand OO better.
"...The chapter 9 describes advice on unit testing such as TDD, keeping tests clean, one assert per test, single concept per test, etc...." Read more
"...It was refreshing to find a book that emphasized the craft of coding - tests, reusability, comments, logging, decoupling, dependency injection,..." Read more
"...Instead, they just said things like, "Design emerges." Again, shallow moral advice that mostly states the obvious with no additional insight..." Read more
"...This book is not just a bunch of theory about how we should make a program cleaner, it has plenty of examples, and it shows how bad code can..." Read more
Customers appreciate the book's maintainability. They find the paperback sturdy and in good condition. The content is in-depth, but it requires time and patience to complete.
"...Learn how to avoid them here. Need code that is readable, maintainable, and usable, but seems like an impossibility?..." Read more
"...authors have of writing code that is not only functional but is maintainable...." Read more
"...developers how they can write code that is more readable and maintainable...." Read more
"...can do to change your code from messy and almost unreadable to highly maintainable with improved comprehension, while discovering previously missed..." Read more
Customers have mixed opinions about the writing quality. Some find the code readable and clear, making it great for intermediate programmers. Others mention that the code snippets are difficult to read and make for a jarring read. The book is described as hard work to learn to write clean code, with the most challenging chapter being refactoring.
"...Code does both, and, like the good code described therein, it’s well written, clear, and easy to read...." Read more
"...Clean code reads like well-written prose...." Read more
"...The contents are NOT common sense and do not come naturally to the uninitiated...." Read more
"...of serious software architecture geeks, with this extraordinary work on writing code well...." Read more
Reviews with images
Good, but tightly coupled to Java and starting to age poorly
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
- Reviewed in the United States on December 29, 2015As CTO of a software company I co-founded, I'm not only looking for books that help me improve individually, but also books that the whole development team – from developers to architects – may find useful. Robert C. Martin’s Clean Code does both, and, like the good code described therein, it’s well written, clear, and easy to read. Martin includes many helpful examples and his suggestions are applicable to any programming language.
Ideally, each developer takes charge of their own education and is constantly improving their skillset, an aspect that Martin covers in The Clean Coder. I view it as an important part of my job to help my team improve. To do so, I distill a lot of written material down to actionable components and provide that to my development team. Concepts from Clean Code have become very helpful guides for them. Below are a few of my favorite takeaways.
The first is what Martin calls The Boy Scout Rule: “Leave the campground a little cleaner than you found it.” It’s a great concept, not only because it's simple to follow, but also because it has broad applicability and can be used on any project. Essentially, when a team member works on a piece of code, they should aim to improve it somehow by the time their task is finished. A few examples of this among many are: fixing an unclear variable name, breaking up a large function into smaller functions, or cleaning up a conditional for improved clarity. With everyone on the team doing this, the code improves over time and everyone feels responsible for the code whether they wrote it personally or not. Even if something can’t be addressed immediately, developers are encouraged to log the issues they see.
Another of my favorite takeaways is the Three Laws of TDD, a concept I was able to quickly roll out to the team as a framework to follow for how TDD should be conducted on a project. This virtually ensures that all of your product code has test coverage. It also helps make most of your code SOLID (https://en.wikipedia.org/wiki/SOLID_%28object-oriented_design%29), since code that is built in this fashion is structured with SOLID concepts in mind. This is a must for effective testing.
Finally, the topics of proper identifier names and commenting really resonated with me and my team. In our company, we tend to “adopt” existing codebases – projects that have already been started by other developers whose code is of widely varying quality. If we're lucky, it's structured well and demonstrates best practices and approaches in how it's constructed. Unfortunately, the code is sloppy at times and requires some TLC to get it in shape. A part of that process is understanding what the existing application does. As Clean Code correctly outlines, many comments are superfluous or even plain wrong and misleading. As a team, we don’t blindly trust the accuracy of existing comments and instead go right to the application’s code to determine what it does. This is where proper naming comes into play. With good names, the code reads like comments or as a narrative of what the application does, nullifying most needs for additional commenting. Simply put, the code comments itself. We also use refactoring tools to improve names and clean up comments as we go. Of course, by doing so, we’re also applying the Boy Scout Rule.
Overall, Clean Code is a wonderful book with much useful and immediately-applicable information for developers of all levels. If you're looking for a book that will help make you a better developer, this will.
- Reviewed in the United States on September 16, 2017As part of our learning activities, we learn quite a few programming languages. We also learn designs, patterns, good coding practices, and many more. We don't usually spend time to learn how to write a good, readable code. The relevance of this book is enormous. Not just the programmers should read it, the education providers should also read it. In fact, the education providers should plan to include this in their curriculum associated with every programming languages.
I started reading this book and finished it in almost three consecutive sittings. That way, the book is well structured, and the topics are well sequenced. The author cautioned at the beginning of the book that it is not for the armchair readers. The reader should spend adequate effort to read through the code examples, think through those, and try out some of those through self scribbling. This is indeed necessary for the coders. This is also necessary for the instructors of coding, or programming languages. I chose to skim through the examples with just enough thinking while paying attention to every detail of the English text. Such speed reading worked for me too. Such reading technique should work for all who are not into direct coding today, but was a programmer once upon a time, and spends a lot of time in conversing with the programmers nowadays.
Coming back to the content of the book - this was quite informative and thought provoking. I read it fully and tried to jot down my takeaways from this book reading. I have got six of them.
I learned the general rules for commenting, and summarized those in four points. I learned the general rules for code formatting, and summarized those in four points. I learned the general practice of code size - for a significant system, for a code file, for a typical function. I learned the general rules of organizing concepts and variables, and summarized those in five points. In fact, the definition of concepts was itself was a new learning for me. I learned the three laws of test driven development, rather I re-learned those once more while reading this book. Finally, I jotted down the final takeaway - leave the code cleaner than what you had started with.
The book is full of good references, in fact at the end of every chapter. I tried to summarize the list of further readings, and I got another five book titles listed in my to-read list. I read it on my Kindle device, and on my desktop using Amazon Cloud Reader - the formatting was good.
As coders, we all have the responsibility to leave the code cleaner than what we start with. As code reviewers, we all have the responsibility to comment on the cleanliness of the codes. As the supervisor or manager of coders, we all have the responsibility to communicate the importance of clean coding and to encourage coders towards clean coding. I will recommend to all these group of people to read this book, and practice the clean coding techniques described here.
Good work indeed!
Top reviews from other countries
- SeekingGoodReviewed in Canada on December 13, 2024
5.0 out of 5 stars Very good!
Very good!
-
AlissonReviewed in Brazil on October 16, 2024
5.0 out of 5 stars Excelente livro
Muito bom, precisa de um tempo para ler. Fundamental
-
Loveen VasnaniReviewed in Spain on November 2, 2024
5.0 out of 5 stars Libro fundamental para los ingenieros
El libro es muy bueno y me ha gustado bastante. El contenido es fácil de leer y los ejemplos son claros en la mayoría de las ocasiones. Este libro es de los mas conocidos en el sector y lo recomiendo a todos los que quieran mejorar sus conocimientos en el área
- The book delivered in two days with a great condition 👍🏻Reviewed in Saudi Arabia on October 31, 2024
5.0 out of 5 stars Amazing
Delivered in Three days in a great condition!
-
Emre AKAReviewed in Turkey on June 25, 2024
5.0 out of 5 stars süper
sağlam şekilde elime ulaştı. teşekkürler