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
1
Section 1
7
Section 2
13
Section 3
19
Section 4
25
Chapter 21
28
License: CyberDojo

Driver/Navigator Switch Techniques

Pair programming encourages participants to switch roles often. These procedures make sure everyone has a chance to drive and navigate. It is crucial that both partners spend an equal amount of time performing each role. There are a few techniques you can use to encourage this.

Chess Clock

Using a chess clock, the pair assigns a time period for performing each role. When the clock rings or a natural breaking point occurs, the pair switches roles.

Ping Pong/Popcorn

  1. A Driver (B Navigator): Writes a new test and sees that it fails for the right reason.
  2. B Driver (A Navigator): Implements the code needed to pass the test.
  3. B Driver (A Navigator): Writes the next test and sees that it fails for the right reason.
  4. A Driver (B Navigator): Implements the code needed to pass the test.
  5. A Driver (B Navigator): Writes the next test and sees that it fails for the right reason.
  6. Rinse and repeat.

    Caution

    If you do not use ping pong...