How to Really Work as a Team - From Sleepy to Strong Pair Programming
summary
Argues that sustained pair programming cuts lead time, smooths pull requests into an ongoing real‑time review, and slashes onboarding time by pairing new hires onto live work; it reports teams surviving two and a half years of lockdown by using Live Share and a pomodoro rhythm to force role switches. Claims pairing for most work is worth the setup cost, warns sleepy driver/navigator modes require discipline, and gives concrete fixes (tight role rules, throwaway phone, commit-and-switch) with teams continuing to use it successfully.
AI-written summary · about
chapters (12)
- 0:00Strong pair programming intro
- 1:31Teams struggle independently
- 6:03Pair programming transforms teams
- 9:58Dangers of sleepy pairing
- 14:14Sleepy driver-navigator roles
- 20:46Distractions for navigators
- 24:42Fixing sleepy driver issues
- 28:14Remote pair programming
- 36:04Key benefits of strong pairing
- 41:23Pair programming for onboarding
- 44:37Why pairing is worth it
- 45:10Q&A
related talks
32mHow to work as a team, sleepy to strong pair programming
56mHow to really work as a team- from sleepy to strong pair programming
23mWarm-Up Talk: Perceptions of Pair Programming
44mWhat We Learned in 8829 Hours of Pair Programming
01h 01mPairing, Sharing, Caring - One team's journey to Pair Programming
30mTo pair or not to pair?
32mMaximizing the Fun Pair Programming Benefits
28mProblem Solving Through Pair Programming