What We Learned in 8829 Hours of Pair Programming
summary
Eight thousand eight hundred and twenty-nine hours of continuous pairing yields specific takeaways: onboarding works in 20 minutes to get up to speed for a single task, pairs rotate on pair rotation weekly, and shared ownership replaces “my code” with frequent refactoring. Pairing styles include ping-pong testing and driver/navigator; remote pairing uses Skype plus shared desktop; productivity per person isn’t doubled but the team ships features faster, finds mistakes earlier, and sustains knowledge across absences.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 2:56Before paring
- 3:41Do they speak their mind
- 5:06Do they know what to do
- 6:24Gary
- 7:05The Development Environment
- 8:01The Pairing Style
- 9:13First Date Mentality
- 10:21Fight Not Fight
- 11:03Noise
- 11:35Kindergarten Skills
- 12:21Story Time
- 13:27Jodi
- 18:13Driver Navigator
- 20:49Code Stewardship
- 23:07Knowledge Area
- 23:37Communication
- 25:49Feedback
- 28:59Ping Pong
- 30:28Trust
- 31:33Practice
- 35:18Sharing Keyboard and Mouse
- 36:01Planning Pairings
- 37:14Human Logic
related talks
23mWarm-Up Talk: Perceptions of Pair Programming
32mMaximizing the Fun Pair Programming Benefits
48mHow to Really Work as a Team - From Sleepy to Strong Pair Programming
01h 01mPairing, Sharing, Caring - One team's journey to Pair Programming
28mProblem Solving Through Pair Programming
30mTo pair or not to pair?
32mHow to work as a team, sleepy to strong pair programming
48m(Remote) Pair programming