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.
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.
这是一本真正的好书,不过如果读者没有一定的经验,以及缺乏对编程境界的追求的话,可能认为这本书很一般,甚至认为只是说了一些大白话。当然,对于有心人来说,这本书里面的很多东西可能都已经习以为常了。我的排序:本书>《代码大全》>《重构》。
评分现在看到那些不好的代码就感觉不舒服,想给改改吧,但又不知道到从和处开刀,挺纠结的,可能是现在火候还不到吧。 现在写代码开始考虑易读性了,以前的想法就是写过的代码从来不会看第二遍,其实这也可能,但是一旦养成个了这个不好的习惯,有一天你想写好让别人能看懂的代码...
评分我一直觉得自己是没脸称自己是个程序员的,但是人渐大每当别人问起”做什么的”的时候,我只好把“写代码”这三个字抛出来,大抵能换到一点对方惊叹和虚荣心的满足,当然在真正的程序员们面前是从来没有得逞过的。 工作两年以来我也试图努力看过《重构》,《代码大全》等书来...
评分看了前几章,大惊! 对自己这几年的积累,还是颇为自信的。想不到短短的几章书,就抵得上我几年的领悟了。 早几年看到这本书,也许现在的水平能再上一个台阶! 强力推荐。 书不见了,还得再买一本了
评分1.这本书的价值超过《代码大全》。它更抽象于一种开发哲学,所以,看不懂,说明你还停留在必须从看得见摸得着的对象学习的程度,对,你需要sample code。 2.只干了一两年程序,或者干了n年程序却一直停留在初级水平的开发人员意识不到这本书的价值。 3.和代码大全一样,这本...
Writing clean code is what you must do in order to call yourself a professional. There is no reasonable excuse for doing anything less than your best.
评分没看完。关于什么是干净的代码,就像是评价什么是好的绘画一样,仁者见仁智者见智。尽管有些公认的标准,但是作者的标准个人并不喜欢。不过在一个大公司,规定统一的风格很重要,无论喜不喜欢,都应遵守。
评分verbose
评分程序员入门书籍
评分和同组同事在周会上读了一年多的书。觉得书中原则可简化成「为之后阅读/修改代码的自己或他人减轻认知负荷」。
本站所有内容均为互联网搜索引擎提供的公开搜索信息,本站不存储任何数据与内容,任何内容与数据均与本站无关,如有需要请联系相关搜索引擎包括但不限于百度,google,bing,sogou 等
© 2025 book.wenda123.org All Rights Reserved. 图书目录大全 版权所有