Clean Code - A Handbook of Agile Software Craftsmanship
Robert C. Martin - Collection Robert C. Martin Series
Résumé
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.
L'auteur - Robert C. Martin
Robert C. Martin est développeur professionnel depuis 1970 et consultant logiciel international depuis 1990. Il est fondateur et directeur général de Object Mentor, Inc., une équipe de consultants expérimentés qui dispense auprès de clients du monde entier des conseils dans plusieurs domaines de l'informatique, comme C++, Java, C#, Ruby, l'orienté objet, les motifs de conception, UML, les méthodes agiles et l'eXtreme Programming.
Photographie : ©Par Angelacleancoder — Travail personnel, CC BY-SA 4.0
Autres livres de Robert C. Martin
Sommaire
- Foreword
- Introduction
- On the Cover
- Clean Code 1
- There Will Be Code 2
- Bad Code 3
- The Total Cost of Owning a Mess 4
- Schools of Thought 12
- We Are Authors 13
- The Boy Scout Rule 14
- Prequel and Principles 15
- Conclusion 15
- Bibliography 15
- Meaningful Names 17
- Introduction 17
- Use Intention-Revealing Names 18
- Avoid Disinformation 19
- Make Meaningful Distinctions 20
- Use Pronounceable Names 21
- Use Searchable Names 22
- Avoid Encodings 23
- Avoid Mental Mapping 25
- Class Names 25
- Method Names 25
- Don't Be Cute 26
- Pick One Word per Concept 26
- Don't Pun 26
- Use Solution Domain Names 27
- Use Problem Domain Names 27
- Add Meaningful Context 27
- Don't Add Gratuitous Context 29
- Final Words 30
- Functions 31
- Small! 34
- Do One Thing 35
- One Level of Abstraction per Function 36
- Switch Statements 37
- Use Descriptive Names 39
- Function Arguments 40
- Have No Side Effects 44
- Command Query Separation 45
- Prefer Exceptions to Returning Error Codes 46
- Don't Repeat Yourself 48
- Structured Programming 48
- How Do You Write Functions Like This? 49
- Conclusion 49
- SetupTeardownIncluder 50
- Bibliography 52
- Comments 53
- Comments Do Not Make Up for Bad Code 55
- Explain Yourself in Code 55
- Good Comments 55
- Bad Comments 59
- Bibliography 74
- Formatting 75
- The Purpose of Formatting 76
- Vertical Formatting 76
- Horizontal Formatting 85
- Team Rules 90
- Uncle Bob's Formatting Rules 90
- Objects and Data Structures 93
- Data Abstraction 93
- Data/Object Anti-Symmetry 95
- The Law of Demeter 97
- Data Transfer Objects 100
- Conclusion 101
- Bibliography 101
- Error Handling 103
- Use Exceptions Rather Than Return Codes 104
- Write Your Try-Catch-Finally Statement First 105
- Use Unchecked Exceptions 106
- Provide Context with Exceptions 107
- Define Exception Classes in Terms of a Caller's Needs 107
- Define the Normal Flow 109
- Don't Return Null 110
- Don't Pass Null 111
- Conclusion 112
- Bibliography 112
- Boundaries 113
- Using Third-Party Code 114
- Exploring and Learning Boundaries 116
- Learning log4j 116
- Learning Tests Are Better Than Free 118
- Using Code That Does Not Yet Exist 118
- Clean Boundaries 120
- Bibliography 120
- Unit Tests 121
- The Three Laws of TDD 122
- Keeping Tests Clean 123
- Clean Tests 124
- One Assert per Test 130
- F.I.R.S.T 132
- Conclusion 133
- Bibliography 133
- Classes 135
- Class Organization 136
- Classes Should Be Small! 136
- Organizing for Change 147
- Bibliography 151
- Systems 153
- How Would You Build a City? 154
- Separate Constructing a System from Using It 154
- Scaling Up 157
- Java Proxies 161
- Pure Java AOP Frameworks 163
- AspectJ Aspects 166
- Test Drive the System Architecture 166
- Optimize Decision Making 167
- Use Standards Wisely, When They Add Demonstrable Value 168
- Systems Need Domain-Specific Languages 168
- Conclusion 169
- Bibliography 169
- Emergence 171
- Getting Clean via Emergent Design 171
- Simple Design Rule 1: Runs All the Tests 172
- Simple Design Rules 2-4: Refactoring 172
- No Duplication 173
- Expressive 175
- Minimal Classes and Methods 176
- Conclusion 176
- Bibliography 176
- Concurrency 177
- Why Concurrency? 178
- Challenges 180
- Concurrency Defense Principles 180
- Know Your Library 182
- Know Your Execution Models 183
- Beware Dependencies Between Synchronized Methods 185
- Keep Synchronized Sections Small 185
- Writing Correct Shut-Down Code Is Hard 186
- Testing Threaded Code 186
- Conclusion 190
- Bibliography 191
- Successive Refinement 193
Caractéristiques techniques
| PAPIER | |
| Éditeur(s) | Prentice Hall |
| Auteur(s) | Robert C. Martin |
| Collection | Robert C. Martin Series |
| Parution | 15/08/2008 |
| Nb. de pages | 464 |
| Format | 17,8 x 23,4 |
| Couverture | Broché |
| Poids | 680g |
| Intérieur | Noir et Blanc |
| EAN13 | 9780132350884 |
| ISBN13 | 978-0-13-235088-4 |
Avantages Eyrolles.com
Consultez aussi
- Les meilleures ventes en Graphisme & Photo
- Les meilleures ventes en Informatique
- Les meilleures ventes en Construction
- Les meilleures ventes en Entreprise & Droit
- Les meilleures ventes en Sciences
- Les meilleures ventes en Littérature
- Les meilleures ventes en Arts & Loisirs
- Les meilleures ventes en Vie pratique
- Les meilleures ventes en Voyage et Tourisme
- Les meilleures ventes en BD et Jeunesse
