How to really work together as a team
summary
Pair programming converts scattered individual work (often one story per developer) into focused, collaborative delivery that cuts lead time and improves PR size and onboarding. Teams use Live Share or shared editing, enforce 25-minute pomodoro rotations to force driver/navigator switches, and tighten driver/navigator definitions so the navigator explains intent while the driver writes their own code. It takes deliberate effort, but teams report smoother reviews, better resilience, and faster delivery when it sticks.
AI-written summary · about
chapters (6)
- 0:00Start
- 9:29Sleepy Pairing
- 36:58Switching Roles
- 42:04Devil's Advocate
- 43:19Collaboration
- 48:41Onboarding Process
related talks
34mPair Programming: Better Than Adderall
41mPair Programming
44mMob Programming: Learn Together. Deliver Together
32mI Have Pair Programmed for 27,000 Hours: Ask Me Anything!
39mMob Programming and the Power of Flow
48mPair Programming, TDD and Other Impractical Things
33mCoaching through Coding
23m10 x your teamwork through pair programming