0%

Book Description

Robert C. Martin reveals the disciplines, techniques, tools, and practices that separate software craftsmen from mere "9-to-5" programmers

  • One of the world's most respected programmers takes software craftsmanship to the next level, answering hard questions about what it really means to be a craftsman

  • Useful advice on how to code, refactor, test, estimate, manage time, and learn

  • By the legendary "Uncle Bob," who helped launch the Agile movement and wrote Software Development's influential "Craftsmanship" column

  • Programming languages and development platforms burst into fashion, and then fade away. Software paradigms briefly dominate, then shift. Methodologies are debated religiously, agreed upon - and soon scrapped altogether. It's no wonder that application development has a high rate of turnover and burnout. Programmers who endure and succeed amidst swirling uncertainty have one thing in common: they all care deeply about the practice of creating software. They treat it as a craft. In this much-anticipated new book, software legend Robert C. Martin explains why programmers should care about their jobs, how organizations can foster the type of environment that allows programmers to succeed, and what it means for individual software developers to truly work as craftsmen. The Clean Coder goes beyond "values and attitudes" to fully document the specific disciplines, techniques, tools, and practices that successful software craftsmen share in common. Throughout his 40-year career at the forefront of movements ranging from agile and extreme programming to object-oriented development, "Uncle Bob" has consistently been a voice of practical common sense and enduring wisdom. He has now written a book that every aspiring and ascending software craftsman can use: to write better software, and to gain greater personal fulfillment in doing so.

    Table of Contents

    1. Title Page
    2. Copyright Page
    3. Contents
    4. Praise for The Clean Coder
    5. Foreword
    6. Preface
    7. Acknowledgments
    8. About the Author
    9. On the Cover
    10. Pre-Requisite Introduction
    11. 1. Professionalism
    12. 2. Saying No
    13. 3. Saying Yes
    14. 4. Coding
    15. 5. Test Driven Development
    16. 6. Practicing
    17. 7. Acceptance Testing
    18. 8. Testing Strategies
    19. 9. Time Management
    20. 10. Estimation
    21. 11. Pressure
    22. 12. Collaboration
    23. 13. Teams and Projects
    24. 14. Mentoring, Apprenticeship, and Craftsmanship
    25. A. Tooling
    26. Index
    27. Footnotes
      1. Pre-Requisite Introduction
      2. Chapter 1
      3. Chapter 2
      4. Chapter 3
      5. Chapter 4
      6. Chapter 5
      7. Chapter 6
      8. Chapter 7
      9. Chapter 8
      10. Chapter 9
      11. Chapter 10
      12. Chapter 12
      13. Chapter 13
      14. Chapter 14
      15. Appendix A
    3.142.173.227