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.
Robert C. “Uncle Bob” Martin has been a software professional since 1970 and an international software consultant since 1990. He is founder and president of Object Mentor, Inc., a team of experienced consultants who mentor their clients worldwide in the fields of C++, Java, C#, Ruby, OO, Design Patterns, UML, Agile Methodologies, and eXtreme programming.
距离第一次看鲍勃大叔的"敏捷开发实践与模式"那本书已经有好多年了, 与那本书相比, 这本书相对来说更强调细节, 如果前一本书强调从大的方面, 比如从设计上, 从方法学上如何写出好的程序, 那么这一本书则是来强调从类的结构, 方法的布局, 变量的命名上阐述如何写出好的代码. 这...
评分我一直觉得自己是没脸称自己是个程序员的,但是人渐大每当别人问起”做什么的”的时候,我只好把“写代码”这三个字抛出来,大抵能换到一点对方惊叹和虚荣心的满足,当然在真正的程序员们面前是从来没有得逞过的。 工作两年以来我也试图努力看过《重构》,《代码大全》等书来...
评分1.这本书的价值超过《代码大全》。它更抽象于一种开发哲学,所以,看不懂,说明你还停留在必须从看得见摸得着的对象学习的程度,对,你需要sample code。 2.只干了一两年程序,或者干了n年程序却一直停留在初级水平的开发人员意识不到这本书的价值。 3.和代码大全一样,这本...
评分公认的翻译比较生硬外,如此书副标题所写:a handbook of agile software craftsmanship. 虽说定义为敏捷软件技能手册,但不失为编码从业人员最基础的职业代码要求规范。
评分我对技术书的要求一向很高,就像我确实很少给一本技术书五星,可是对这本书,我在读到一半的时候,就已经迫不及待把他标志成五星书籍。 在和朋友聊到这本书的时候,朋友谈到,其实书里的道理非常浅显,每个人都知道,只是我们到真的去用的时候就忘记了,或者为了省事就不去注...
god is in the detail!
评分真心建议每个写程序的都熟读牢记应用,这样同僚的WTF/minute真心会减少很多
评分略
评分和同组同事在周会上读了一年多的书。觉得书中原则可简化成「为之后阅读/修改代码的自己或他人减轻认知负荷」。
评分这些看似不高的要求,实际上要求非常高。想来如果代码都写的费劲的话,怎么会去考虑这些东西,所以说还是抓紧提高自己的编程能力吧
本站所有内容均为互联网搜索引擎提供的公开搜索信息,本站不存储任何数据与内容,任何内容与数据均与本站无关,如有需要请联系相关搜索引擎包括但不限于百度,google,bing,sogou 等
© 2025 book.quotespace.org All Rights Reserved. 小美书屋 版权所有