Clean Code: A Handbook of Agile Software Craftsmanship
Clean Code: A Handbook of Agile Software Craftsmanship
复制标题
干净的代码：敏捷软件工艺手册
DOI：
--
复制
发表时间：
2008
期刊：
影响因子：
--
通讯作者：
Robert C. Martin
中科院分区：
文献类型：
--
作者：
Robert C. Martin
即使是坏代码也可以起作用。但是，如果代码不干净，它可以使开发组织屈膝。每年，由于书面代码不佳，每年无数小时和大量资源都会丢失。但这并不一定是那样的。专家罗伯特·马丁（Robert C.马丁（Martin）帮助将敏捷的原则从从业人员的角度带到了成千上万的程序员，他与对象导师的同事合作，将他们的最佳敏捷态度清除代码提炼成一本书，将其灌输到您的内部。软件工匠的价值，只有在您工作时才能使您成为更好的程序员。您将做什么样的工作？您将阅读代码的编码器。您将挑战考虑该代码的正确内容以及它的问题。更重要的是，您将受到挑战，以重新评估您的专业价值观和对手艺的承诺。干净的代码分为三个部分。第一个描述编写干净代码的原理，模式和实践。第二部分由数个复杂性增加的案例研究组成。每个案例研究都是一种练习，以清理将代码基库的代码库清理为有效和高效的代码库。第三部分是回报：一章，其中包含在创建案例研究时收集的启发式和气味的清单。结果是一个知识库，描述了我们在编写，阅读和清洁代码时思考的方式。阅读器将从本书中脱颖而出，以说明好代码和坏代码方式之间的区别以编写好代码以及如何将坏代码转换为良好的代码方式可以创建好名字，好功能，好的对象和良好的课堂，以格式化代码，以实现最大的可读性，如何实现完整的错误处理而不将代码logichow掩盖到单位测试和练习测试驱动的开发内容和启发式的启发式和启发式方法可以帮助您识别不良的Codethis对于任何有兴趣制作更好的代码的开发人员，软件工程师，项目经理，团队负责人或系统分析师来说，书都是必不可少的。
Even bad code can function. But if code isnt 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 doesnt 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 practitioners 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 programmerbut only if you work at it.What kind of work will you be doing? Youll be reading codelots of code. And you will be challenged to think about whats right about that code, and whats 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 codeof 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 understandingHow to tell the difference between good and bad codeHow to write good code and how to transform bad code into good codeHow to create good names, good functions, good objects, and good classesHow to format code for maximum readability How to implement complete error handling without obscuring code logicHow to unit test and practice test-driven developmentWhat smells and heuristics can help you identify bad codeThis book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.