หนังสือ · 2008
Clean Code : A Handbook of Agile Software Craftsmanship
ยังไม่มีตัวเล่มในห้องสมุด
ตัวเล่มในห้องสมุด
ห้องสมุดยังไม่มีตัวเล่มของรายการนี้
รายละเอียด
- ชื่อเรื่อง
- Clean Code : A Handbook of Agile Software Craftsmanship
- ผู้แต่ง
- Martin, Robert C.
- พิมพ์ที่
- Prentice Hall, 2008
- ภาษา
- อังกฤษ
- ISBN
- 9780132350884
- หมายเหตุ
- Foreword -- Introduction -- On the Cover -- Clean Code -- There Will Be Code -- Bad Code -- The Total Cost of Owning a Mess -- The Grand Redesign in the Sky -- Attitude -- The Primal Conundrum -- The Art of Clean Code? -- What Is Clean Code? -- Schools of Thought -- We Are Authors -- The Boy Scout Rule -- Prequel and Principles -- Conclusion -- Bibliography -- Meaningful Names -- A Introduction -- Use Intention-Revealing Names -- Avoid Disinformation -- Make Meaningful Distinctions -- Use Pronounceable Names -- Use Searchable Names -- Avoid Encodings -- Hungarian Notation -- Member Prefixes -- Interfaces and Implementations -- Avoid Mental Mapping -- Class Names -- Method Names -- Don't Be Cute -- Pick One Word per Concept -- Don't Pun -- Use Solution Domain Names -- Use Problem Domain Names -- Add Meaningful Context -- Don't Add Gratuitous Context -- Final Words -- Functions -- Small! -- Blocks and Indenting -- Do One Thing -- Sections within Functions -- One Level of Abstraction per Function -- Reading Code from Top to Bottom: The Stepdown Rule -- Switch Statements -- Use Descriptive Names -- Function Arguments -- Common Monadic Forms -- Flag Arguments -- Dyadic Functions -- Triads -- Argument Objects -- Argument Lists -- Verbs and Keywords -- Have No Side Effects -- Output Arguments -- Command Query Separation -- Prefer Exceptions to Returning Error Codes -- Extract Try/Catch Blocks -- Error Handling Is One Thing -- The Error.java Dependency Magnet -- Don't Repeat Yourself -- Structured Programming -- How Do You Write Functions Like This? -- SetupTeardownIncluder -- Comments -- Comments Do Not Make Up for Bad Code -- Explain Yourself in Code -- Good Comments -- Legal Comments -- Informative Comments -- Explanation of Intent -- Clarification -- Warning of Consequences -- TODO Comments -- Amplification -- Javadocs in Public APIs -- Bad Comments -- Mumbling -- Redundant Comments -- Misleading Comments -- Mandated Comments -- Journal Comments -- Noise Comments -- Sca 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, tea