How to work as a team, sleepy to strong pair programming
summary
Claim: pairing moves value faster and reduces silos when practiced with concrete habits. Removes distractions (phones out of reach), expands driver/navigator into explain then code role switching, and uses tools like Live Share for remote sessions. Teams keep PRs small, onboard new hires immediately, and scale rapidly — one project grows from one team to three teams in a day (threefold increase). Fixes are collaborative, WIP drops, and sleepy pairing is replaced by active pairing.
AI-written summary · about
chapters (8)
- 0:00Start
- 5:46Sleepy Pairing
- 12:15The Sleepy Navigator
- 17:17Sleepy Pairing into Strong Pairing
- 19:24Onboarding
- 23:47Optimal Timing
- 27:54Context Switching
- 31:33Parting Thoughts
related talks
48mHow to Really Work as a Team - From Sleepy to Strong Pair Programming
56mHow to really work as a team- from sleepy to strong pair programming
01h 01mPairing, Sharing, Caring - One team's journey to Pair Programming
23mWarm-Up Talk: Perceptions of Pair Programming
44mWhat We Learned in 8829 Hours of Pair Programming
30mTo pair or not to pair?
28mProblem Solving Through Pair Programming
28mPair Programming as a Mechanism for Growth