Clean Code: A Handbook Of Agile Software Craftsmanship
ISBN: 0132350882
EAN13: 9780132350884
Language: English
Release Date: Aug 1, 2008
Pages: 464
Dimensions: 1.2" H x 9.2" L x 7" W
Weight: 1.7 lbs.
Format: Paperback
Publisher:
Select Format Format: Paperback Select Conditions Condition: New

Selected

Format: Paperback

Condition: New

$49.99
Quantity
Almost Gone!
Only 4 at this price.

Select Conditions
  • New $49.99 Clean Code: A Handbook Of Agile Software Craftsmanship
Book Overview

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, 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 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 Read More chevron_right

Frequently Asked Questions About Clean Code: A Handbook Of Agile Software Craftsmanship

Book Reviews (12)

4
  |   12  reviews
Did you read Clean Code: A Handbook Of Agile Software Craftsmanship? Please provide your feedback and rating to help other readers.
Write Review
Captcha
5
   Swallowed My Pride and bought this book
I have been programming for about 17 years and consider myself an above average programmer. But this book made me feel like I am actually a terrible coder. I've always gotten my tasks done, but I didn 't pay attention to refactoring to clean up the code. I don't have much to do yet and got a demo coming up in a few days. As I read my uncoded verdicts on all his examples of bad code '', it inspires me to care again about coding ''. It can be funny and it is not all about getting the job done. What is sad about the reality is that bad code '' will continue growing over time because people don 't realize what bad code '' can do in the long run. The programmer must read this book, regardless of experience. Merci beaucoup!
 
5
   Great book that makes you question your coding style
I think that every beginner to intermediate programmer should read this book even if you don 't agree with everything in the book. It makes you question your coding styles and methods. It makes you question your coding methods. My primary language is c# and almost everything is translated perfectly. After reading this, I would say I was a better coder if I would defiantly say .
 
5
   Game Changer
I had really high expectations of what this book was and it seemed to meet every single one of them! '' I would be remiss to say that it did not change my outlook on the way I write my own code as a mid-level developer. Although there is a class per SQL Add, Update, Delete method in a particular instance, I think the emphasis on classes was a little overboard. However, every other was extremely justifiable and correct.
 
5
   Good advice delivered clearly and directly with examples
While this book includes many things I already knew, such as the law of Demeter, it touches them in a thorough and interesting way. Examples are all in Java, which, though not my primary programming language, carries many of the same benefits and pitfalls of any other OO language. This book is also a great motivation. Many of us know that we need to write cleaner code, but the pressure of our peers or timelines often makes us forget, or at least ignore, this impulse, often to our own detriment. I have it on my desk as I have not yet finished it, but even when I have a day where I don 't read out of it, it serves as a reminder of what I should be doing. This book will not disappoint you if you want to make yourself a better programmer.
 
1
   Don't bother unless you know java
Just a bunch of Java densely compacted on half a page and difficult to read. In my copy, there is no indentation, impossible to read.
 
1
   Dogmatic rehashing of outdated truisms
Stay away from this book and stay away from it. It's a one-person ramble about his preferences in coding. Plus, he turns everything into a moral issue about being a “professional”. If you earn money with the craft, period, you are a professional if you are a professional. This is what the term “ Profession ” means. The rest are dogmas of Bob's cult, akin to Pythagoreans abstaining eating beans. Go to his GitHub page and see for yourself whether you like his “clean code . I don 't ''.
 
5
   A must for any coder
This got this as a graduation present for a friend. This book is a must-have for anyone who is serious about being a professional coder.
 
2
   Java & OOP centered
Stay far away from this book, you are not an OOP programmer. All examples are in Java, but most C++ programmers should be able to translate the ideas mentally. There is also too much focus on Java - specific tooling. While there are some good points that this book makes, it ignores many good programming techniques used in standard imperative languages without objects. It completely disregards functional languages and gives some terrible advice when it comes to writing good code in a functional style. It is pretty good up to chapter 7 in general. After that, it is pretty much downhill.
 
4
   Good, but tightly coupled to Java and starting to age poorly
3.5 stars : Much of the information in this book is eye opening, particularly the chapters on functions, classes and code smells. A serious problem is that this book is very Java-centric and is clearly a product of its copyright date 2009. Many of the chapters have been made moot, and a few aren't fully applicable to any other language. Note also about buying a new, physical version from Amazon. The book will be damaged in shipping, as it comes in a padded envelope and will be used like a padded book before you receive it. See my picture.
 
2
   The content is good, but the soft cover version of the book ...
The content is good, but the poor cover version of the book is of a soft print quality, it looks like it was printed from photocopies. I heard that originally the print quality was ok, well, it is not anymore. It is still readable, but I would never buy it if I knew something about the printing quality. Other reviews should have been read.
 
12