Clean Coder, The

Robert C. Martin (“Uncle Bob”) has been a programmer since 1970. He is founder and president of Object Mentor, Inc., an international firm of highly experienced software developers and managers who specialize in helping companies get their projects done. Object Mentor offers process improvement consulting, object-oriented software design consulting, training, and skill development services to major corporations worldwide. Martin has published dozens of articles in various trade journals and is a regular speaker at international conferences and trade shows.He has authored and edited many books, including: Designing Object Oriented C++ Applications Using the Booch MethodPatterns Languages of Program Design 3More C++ GemsExtreme Programming in PracticeAgile Software Development: Principles, Patterns, and PracticesUML for Java ProgrammersClean Code A leader in the industry of software development, Martin served for three years as editor-in-chief of the C++ Report, and he served as the first chairman of the Agile Alliance.Robert is also the founder of Uncle Bob Consulting, LLC, and cofounder with his son Micah Martin of The Clean Coders LLC.

"'Uncle Bob' Martin definitely raises the bar with his latest book. He explains his expectation for a professional programmer on management interactions, time management, pressure, on collaboration, and on the choice of tools to use. Beyond TDD and ATDD, Martin explains what every programmer who considers him- or herself a professional not only needs to know, but also needs to follow in order to make the young profession of software development grow." -Markus Gartner Senior Software Developer it-agile GmbH www.it-agile.de www.shino.de "Some technical books inspire and teach; some delight and amuse. Rarely does a technical book do all four of these things. Robert Martin's always have for me and The Clean Coder is no exception. Read, learn, and live the lessons in this book and you can accurately call yourself a software professional." -George Bullock Senior Program Manager Microsoft Corp. "If a computer science degree had 'required reading for after you graduate,' this would be it. In the real world, your bad code doesn't vanish when the semester's over, you don't get an A for marathon coding the night before an assignment's due, and, worst of all, you have to deal with people. So, coding gurus are not necessarily professionals. The Clean Coder describes the journey to professionalism ... and it does a remarkably entertaining job of it." -Jeff Overbey University of Illinois at Urbana-Champaign "The Clean Coder is much more than a set of rules or guidelines. It contains hard-earned wisdom and knowledge that is normally obtained through many years of trial and error or by working as an apprentice to a master craftsman. If you call yourself a software professional, you need this book." -R. L. Bogetti Lead System Designer Baxter Healthcare www.RLBogetti.com

• Foreword xiii Preface xixAcknowledgments xxiiiAbout the Author xxixOn the Cover xxxiPre-Requisite Introduction 1Chapter 1: Professionalism 7Be Careful What You Ask For 8Taking Responsibility 8First, Do No Harm 11Work Ethic 16Bibliography 22Chapter 2: Saying No 23Adversarial Roles 26High Stakes 29Being a “Team Player” 30The Cost of Saying Yes 36Code Impossible 41Chapter 3: Saying Yes 45A Language of Commitment 47Learning How to Say “Yes” 52Conclusion 56Chapter 4: Coding 57Preparedness 58The Flow Zone 62Writer’s Block 64Debugging 66Pacing Yourself 69Being Late 71Help 73Bibliography 76Chapter 5: Test Driven Development 77The Jury Is In 79The Three Laws of TDD 79What TDD Is Not 83Bibliography 84Chapter 6: Practicing 85Some Background on Practicing 86The Coding Dojo 89Broadening Your Experience 93Conclusion 94Bibliography 94Chapter 7: Acceptance Testing 95Communicating Requirements 95Acceptance Tests 100Conclusion 111Chapter 8: Testing Strategies 113QA Should Find Nothing 114The Test Automation Pyramid 115Conclusion 119Bibliography 119Chapter 9: Time Management 121Meetings 122Focus-Manna 127Time Boxing and Tomatoes 130Avoidance 131Blind Alleys 131Marshes, Bogs, Swamps, and Other Messes 132Conclusion 133Chapter 10: Estimation 135What Is an Estimate? 138PERT 141Estimating Tasks 144The Law of Large Numbers 147Conclusion 147Bibliography 148Chapter 11: Pressure 149Avoiding Pressure 151Handling Pressure 153Conclusion 155Chapter 12: Collaboration 157Programmers versus People 159Cerebellums 164Conclusion 166Chapter 13: Teams and Projects 167Does It Blend? 168Conclusion 171Bibliography 171Chapter 14: Mentoring, Apprenticeship, and Craftsmanship 173Degrees of Failure 174Mentoring 174Apprenticeship 180Craftsmanship 184Conclusion 185Appendix A: Tooling 187Tools 189Source Code Control 189IDE/Editor 194Issue Tracking 196Continuous Build 197Unit Testing Tools 198Component Testing Tools 199Integration Testing Tools 200UML/MDA 201Conclusion 204Index 205