- Series: Robert C. Martin Series
- Paperback: 256 pages
- Publisher: Prentice Hall; 1 edition (May 23, 2011)
- Language: English
- ISBN-10: 0137081073
- ISBN-13: 978-0137081073
- Product Dimensions: 7 x 1 x 9 inches
- Shipping Weight: 14.9 ounces (View shipping rates and policies)
- Average Customer Review: 140 customer reviews
- Amazon Best Sellers Rank: #15,312 in Books (See Top 100 in Books)
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.
The Clean Coder: A Code of Conduct for Professional Programmers 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
This item, sold by Amazon.com, is currently reserved exclusively for Prime members.
- Unlimited Free Two-Day Shipping
- Instant streaming of over 40,000 movies and TV episodes
- A Kindle book to borrow for free each month - with no due dates
- Over a million songs and hundreds of playlists
Also available to Amazon Students. Check for eligibility
Customers who bought this item also bought
Customers who viewed this item also viewed
What other items do customers buy after viewing this item?
From the Publisher
|A Handbook of Agile Software Craftsmanship||Practical Advice for the Professional Programmer||A Craftsman's Guide to Software Structure and Design||Professionalism, Pragmatism, Pride||Get Better Performance Out of Your Legacy Systems|
|Title||Clean Code||Clean Coder||Clean Architecture||The Software Craftsman||Working Effectively with Legacy Code|
|Core Concept||Best agile practices of cleaning code “on the fly” that will instill within you the values of a software craftsman and make you a better programmer—but only if you work at it.||Robert C. 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.||Uncle Bob presents the universal rules of software architecture that will help you dramatically improve developer productivity throughout the life of any software system.||Sandro Mancuso helped found the world’s largest organization of software craftsmen; now, he shares what he’s learned through inspiring examples and pragmatic advice you can use in your company, your projects, and your career.||Is your code easy to change? Can you get nearly instantaneous feedback when you do change it? Do you understand it? If the answer to any of these questions is no, you have legacy code, and it is draining time and money away from your development efforts. Michael Feathers offers start-to-finish strategies for working more effectively with large, untested legacy code bases.|
|Endoresement||"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. Read, learn, and live the lessons in this book and you can accurately call yourself a software professional.” —George Bullock Senior Program Manager Microsoft Corp.||"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||"If you are the type of programmer, team lead, or manager who craves to be able to go home after a long day of work, look in the mirror, and say, 'Damn, I did a good job today!' then this is the book for you." -- Robert C. Martin||"This book describes a set of disciplines, concepts, and attitudes that you will carry with you for the rest of your career and that will help you to turn systems that gradually degrade into systems that gradually improve." --- Robert C. Martin|
“‘Uncle Bob’ Martin definitely raises the bar with his latest book. He explains his expectation for a professional programmer on management interactions, time management, pressure, on collaboration, and on the choice of tools to use. Beyond TDD and ATDD, Martin explains what every programmer who considers him- or herself a professional not only needs to know, but also needs to follow in order to make the young profession of software development grow.”
Senior Software Developer
“Some technical books inspire and teach; some delight and amuse. Rarely does a technical book do all four of these things. Robert Martin’s always have for me and The Clean Coder is no exception. Read, learn, and live the lessons in this book and you can accurately call yourself a software professional.”
Senior Program Manager
“If a computer science degree had ‘required reading for after you graduate,’ this would be it. In the real world, your bad code doesn’t vanish when the semester’s over, you don’t get an A for marathon coding the night before an assignment’s due, and, worst of all, you have to deal with people. So, coding gurus are not necessarily professionals. The Clean Coder describes the journey to professionalism . . . and it does a remarkably entertaining job of it.”
University of Illinois at Urbana-Champaign
“The Clean Coder is much more than a set of rules or guidelines. It contains hard-earned wisdom and knowledge that is normally obtained through many years of trial and error or by working as an apprentice to a master craftsman. If you call yourself a software professional, you need this book.”
–R. L. Bogetti
Lead System Designer
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 codeHow to write good code and how to transform bad code into good codeHow to create good names, good functions, good objects, and good classesHow to format code for maximum readabilityHow to implement complete error handling without obscuring code logicHow to unit test and practice test-driven developmentThis book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
There are many other books that teach you how to write good code - that is not the purpose of this book. Rather, Uncle Bob strives to show you how to be a good professional, and all that entails. If the concept makes you want to sneer, don't - there are lots of behaviors that we'd normally do which are not professional and hurt both your company as yourself. Have you ever said "yes" when pressed to commit to an unreasonable deadline? Pushed half-done work through? Given overly optimistic estimations that people thought of as deadlines? Felt forced to wade through a mess of (partly) your own making? Well, even if you haven't, odds are that you will at some time, as (sadly) every developer finds themselves at such situations at some point during this career. What this book aims to do is to help you identify these situations, explain why these are harmful and provide you with the tools to better respond to these. Oh, and of course, expect the usual useful insight on how to improve your programming practices.
While Clean Code was a bit hard to read sometimes and made you stop every now and then, if only to get a better grasp of the concepts, this one feels so relatable that it reads in a breeze. What more can you ask for?
Our craft would be a lot better if every programmer was given a copy of this before they started working. Or at the very least, I am certain that this book has helped me become a better professional and I expect its teachings will continue to do so.
I gave it 4 instead of 5 stars because I can see some younger programmers failing to get invested in the narrative of this book, simply because there is a lot of examples provided of how things were back in the 70s and 80s doing development on paper tape and punch cards, and if you fail to grasp that these are stories that elucidate where the bad practices we deal with today originate, then you may yawn, skip, or simply put down the book.
Tips to potential readers of this book: the talk about the old days of programming, read it with the understanding that it is a history lesson into why the SDLC has faults, where they come from and why they exist. The talk about FITNesse being the absolute solution to all your woes is sadly a really bad attempt at self-promotion, so you should take away why you would use FITNesse, and draw your own conclusions as to whether it or another tool would do the same task for your business. Also, don't be discouraged by your business in that you can't change all the bad practices overnight, just remember, there are measures you can control, so do so and encourage other developers in your section to do the same, eventually you can at least carve out a little professionalism in your day to day.