Warm-Up Talk: Perceptions of Pair Programming
summary
Argues that pair programming produces concrete outcomes: faster competency, more robust code, fewer knowledge islands and shared ownership. Describes using weekly dev couch and cross-team code reviews, regular sessions that become three to four hour blocks or months of pairing even six to eight hours a day, and tooling like VS Code and remote screen sharing for distributed pair programming. Explains specific workflows — driver-navigator, backseat navigator, tour guide, and ping pong pairing — and gives stories where pairing measurably speeds onboarding and reduces bugs.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:06What is pair programming?
- 3:41My experiences
- 8:04Others' experiences
- 11:07There's no roadmap
- 11:36Types
- 11:56Driver - Navigator
- 12:23Backseat Navigator
- 12:56Tour Guide
- 13:35Ping-Pong
related talks
01h 01mPairing, Sharing, Caring - One team's journey to Pair Programming
44mWhat We Learned in 8829 Hours of Pair Programming
48mHow to Really Work as a Team - From Sleepy to Strong Pair Programming
28mProblem Solving Through Pair Programming
32mMaximizing the Fun Pair Programming Benefits
28mPair Programming as a Mechanism for Growth
41mPair Programming
32mHow to work as a team, sleepy to strong pair programming