Pairing, Sharing, Caring - One team's journey to Pair Programming
summary
A team moves from silos to near-continuous pairing, proving the claim that pairing raises code quality and shared product knowledge: they push monitors together, adopt Code With Me and VS Code/Fluobits for remote sessions, add git-mit so commits show coauthors, and drop heavy reviews in favor of trunk-based development and effectively no PRs. Rotation, driver/navigator and ping‑pong styles spread knowledge, shorten feedback loops, cut on‑call stress and make holidays genuinely restful — the experiment scales and sticks.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 1:18What pair programming is
- 3:05Team’s communication problem
- 4:29Offsite training enthusiasm
- 5:13First failed pairing attempt
- 7:21Why team needed pairing
- 11:10Pairing revival backend
- 12:59Starting small affordable
- 14:45Cross-functional pairing frontend
- 17:15Year-long journey pairing
- 18:18Pairing benefits beyond coding
- 20:27Pair programming styles
- 23:55Team bonding psychological safety
- 26:45Remote pair programming
- 30:47Tips for successful pairing
- 35:43Avoiding pairing distractions
- 37:50When not to pair
- 38:54Tools for code ownership
- 39:59Pair programming books
- 41:23Feedback and improvement
- 42:29Pairing challenges downsides
- 46:21Thinking out loud for experienced developers
- 48:27Conflict resolution pairing
- 50:58Moving from pull requests
- 53:31Adapting brain rhythms pairing
- 55:56Whiteboards in pairing
- 58:04Convincing management
related talks
23mWarm-Up Talk: Perceptions of Pair Programming
32mHow to work as a team, sleepy to strong pair programming
32mMaximizing the Fun Pair Programming Benefits
56mHow to really work as a team- from sleepy to strong pair programming
44mWhat We Learned in 8829 Hours of Pair Programming
28mProblem Solving Through Pair Programming
48mHow to Really Work as a Team - From Sleepy to Strong Pair Programming
57mRemote Pairing