Book Image

Agile Technical Practices Distilled

By : Pedro M. Santos, Marco Consolaro, Alessandro Di Gioia
Book Image

Agile Technical Practices Distilled

By: Pedro M. Santos, Marco Consolaro, Alessandro Di Gioia

Overview of this book

The number of popular technical practices has grown exponentially in the last few years. Learning the common fundamental software development practices can help you become a better programmer. This book uses the term Agile as a wide umbrella and covers Agile principles and practices, as well as most methodologies associated with it. You’ll begin by discovering how driver-navigator, chess clock, and other techniques used in the pair programming approach introduce discipline while writing code. You’ll then learn to safely change the design of your code using refactoring. While learning these techniques, you’ll also explore various best practices to write efficient tests. The concluding chapters of the book delve deep into the SOLID principles - the five design principles that you can use to make your software more understandable, flexible and maintainable. By the end of the book, you will have discovered new ideas for improving your software design skills, the relationship within your team, and the way your business works.
Table of Contents (31 chapters)
Free Chapter
Section 1
Section 2
Section 3
Section 4
Chapter 21
License: CyberDojo

Classic TDD

Classic TDD is the original approach to TDD created by Kent Beck. It is also known as the Detroit/Chicago school of TDD. This practice allows you to:

  • Spend less time debugging code to prove that it works: Tests will show that your code works correctly and implements the expected behavior.
  • Reduce the fear of changing code: Tests act as a safety net. Would you walk on a rope several hundred feet high? What if you had a safety net? TDD is your safety net.
  • Use tests as living documentation: Well-crafted tests describe the behavior in your code, and above all, serve as up-to-date documentation.
  • Use tests as a feedback loop for design decisions: If tests are difficult to write, your design can probably be improved.