Strong-Style Pair Programming
Last updated on 2018-12-27
About the Book
Pair programming is fun and engaging, and while it may make you slower, it also effectively takes best of the both into the work being done resulting in better code and better programmers in the long term.
A pair driving a car together has usually trained together, share a vocabulary and while striving for the same goal, they have their own tasks to do.
In strong-style pairing, the foundation of the tasks is that the idea (and high-level control) of the task is not with the person on they keyboard.
In traditional-style pairing, the idea is with the person on the keyboard.
For strong-style pair programming we say: "Take the keyboard, I have an idea" and navigate the implementation on highest possible level of abstraction. The review happens with the person on the keyboard, on their terms and pace as it flows through their hands.
Strong-style pair programming is particularly well suited for engaging uneven pairs and people new to pairing. Is your style intentional or accidental?
What is Strong-Style Pair Programming
- Strong-Style Pair Programming Defined
- Strong-Style Pairing on Selenium tests
- Good Pairing Gives You…
Story from Early Days
- Learned at Agile 2015
- What is there here?
- Don’t be a Backseat driver
Styles of Pairing
- Individual Work
- Traditional Pairing
- Strong-Style Pairing
- Different Skillsets, Unequal at a Task
- Mob Programming — Pairing on Turned Up
Driver and Navigator in Strong-Style Pairing
- Getting Set Up For Pairing
- Who Should Drive and Who Should Navigate?
- Driver: Things to Do
- Navigator: Things to Do
- Closure Activities
- Ending this with a word of warning
Collaborate Beyond Pairing
- Side by Side Pairing - the Expert Flavor
- Side by Side Pairing - the Two Drivers Flavor
- Two People Who Get Me To Do Stuff
The Leanpub 45-day 100% Happiness Guarantee
Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
See full terms...