I've Pair Programmed for 27,000 Hours. Ask Me Anythings!
summary
Claims nearly 13½ years of near‑daily pairing and four years full‑time remote, and cites an empirical ~15% slow‑down in controlled studies. Describes concrete tools—video chat, screen sharing—and concrete practices: Pivotal Tracker and Floobits, daily rotation and ping‑pong pairing. Lists measurable outcomes: cross‑training, fewer bugs, better factoring, and tactics for measuring and selling pairing. Gives numbers, tradeoffs, when to skip pairing for tiny tasks, and when promiscuous pairing or enforced rotation helps.
AI-written summary · about
chapters (4)
- 0:00Start
- 1:58WHAT IS BENEFITS OF PAIR
- 2:47WHAT ARE THE CHALLENGES OF PAIR PROGRAMMING?
- 3:26WHEN DO YOU GO TO THE BATHROOM?
related talks
32mI Have Pair Programmed for 27,000 Hours: Ask Me Anything!
32mMaximizing the Fun Pair Programming Benefits
41mto-Peer PowerShell: The Ins and Outs of Pair Programming
49mApprenticeship programs
23mWorking Together: Pairing as Senior and Junior Developers
53mHalf a decade of mob programming
11mProgramming Like An Athlete
18mProgramming Workout