Clean Code: A Handbook of Agile Software Craftsmanship
著者: -
|
|
| Paperback: | 464 ページ |
| 出版社: | Prentice Hall |
| 出版日: | 2008年8月11日 |
| ISBN: | 0132350882 |
| ISBN-13: | 9780132350884 |
| 参考価格: | $47.99 |
| 価格: | $39.11 ($8.88 off) |
 |
 （1冊目 / 2冊目以降） |
 （1冊目 / 2冊目以降） |
|
|---|---|---|---|
| 価格 | - | ￥3,504 | - |
| 送料 | ￥805 / ￥358 | ||
| 合計 | ￥4,309 / ￥3,862 | ||
| 発送 | Usually ships in 24 hours | ||
| 購入 |
|
||
|
|||
関連商品
内容説明
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
カスタマーレビュー
日本
米国
- レビュー数: 69件
- 平均評価:
: Dejung None - 2010年7月27日Clean Code: A Handbook of Agile Software Craftsmanship
This book is far better then I expected. Much more in depth and looking at real codeing problems and shows great ways to solve them.
Excelent book there should be more like this one out there :)
: MesSer None - 2010年7月26日Excellent book
I'd recommend everybody to read this book. Many good examples and practices and it's all written in a way that is easy to follow.
The most important lesson from this book is : "Make it testable, do an easy implementation, make it work then improve it". There are many good guidelines that are introduced in this book and I think that the way you think about code and about programming will change after reading this book.
: Jesper Kolbeck None - 2010年5月6日Great book
I don't agree with everything in this book, but it makes me think about the code I write and change it to the better.
: Felix Siegrist Switzerland - 2010年4月23日Great Book
I like this book very much. Reading it can change your attitude against your job as a software developer.
For readers interested in an errata page, see http://www.engineering.uiowa.edu/~wwalls/clean_code_errata/.
: arzewski pittsburgh, pa United States - 2010年4月20日uneven, unbalanced
I was looking forward to read this, given the very interesting literature I have read in the past years that was authored by the book author. But somehow, something about his book let me down, and returned it. There are some books that I go back to them to read upon again on a chaper or passage, get more insight, or show it to a collegue. One such book could be "Refactoring to Patterns". But this book doesn't have that quality in balance of prose and presentation. Some chapters are surprisingly small. One chapter, loaded with a case study of code refactoring, is huge. Also, the illustrations, although funny at times, give somewhat of an amateurish imprint to the overall book image. I got somewhat an impression that it was an amalgamation of several past years of slides and presentations and tutorials, collected together. Also, the usage of "bean" as a word is so passe'. Yes, all examples are in Java (nothing wrong with that, but keep the programming-language-specific terminology out... Joshua Bloch wrote "Effective Java" and it is being read by C# programmers as well)
