| Can I Come Look At These Items? | | This online store is in association with Amazon.com, so these great, high-qualiy products will come from their warehouse or from other partners. Thanks for shopping! |
|
|
|
Clean Code: A Handbook of Agile Software Craftsmanship (Robert C. Martin Series) | 
 enlarge | Author: Robert C. Martin
Publisher: Prentice Hall PTR
Category: Book
List Price: $42.99
Buy New: $26.90
You Save: $16.09 (37%)
New (15) Used (1) from $26.90
Avg. Customer Rating:  1 reviews
Sales Rank: 6701
Media: Paperback
Edition: 1
Number Of Items: 1
Pages: 464
Shipping Weight (lbs): 1.5
Dimensions (in): 9.2 x 6.9 x 1
ISBN: 0132350882
Dewey Decimal Number: 005.1
EAN: 9780132350884
ASIN: 0132350882
Publication Date: August 11, 2008 (New: Last 30 Days)
Availability: Usually ships in 1-2 business days
Shipping: Expedited shipping available
Shipping: International shipping available
Condition: Paperback. Perfect condition. Never used. Great book.
|
| Similar Items:
|
| Editorial Reviews:
Product Description
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.
|
| Customer Reviews:
Good book but consider Kent Beck's "Implementation Patterns" first. August 19, 2008
0 out of 1 found this review helpful
If I had not read Kent Beck's excellent "Implementation Patterns" book, I might have been more impressed by "Clean Code". I prefer "Implementation Patterns" because it is more concise, and was easier for me to internalize.
If you are the type of person who enjoys doing book exercises (or is self-disciplined enough to do them), then "Clean Code" has plenty of exercises.
If you are self-disciplined enough to do book exercises, you might want to buy "Implementation Patterns", then pick an Open Source project (like JUnit, ant, etc.) (if it has unit tests then that's all the better) and then try to find places in the code where the principles are used and where they're not. Then refactor the code (see "Refactoring" by Martin Fowler) to use Kent's principles.
If you're a Smalltalker, you may prefer Kent Beck's excellent "Smalltalk Best Practice Patterns" which has a similar intent to the "Implementation Patterns" book but is geared towards the Smalltalk language and libraries.
If you follow Kent Beck's advice, you will write Clean Code (and you'll only have to read 148 pages as opposed to the 464 pages of "Clean Code").
|
|
|
| |
News 
