The developers worked in two by two. Hurrah! Hurrah!
summary
Pair programming remains a practiced, measurable approach: teams at LMAX run it as core practice for over 15 years, pairing on dual-keyboard stations or remotely via VNC/Zoom, and report roughly 15% higher cost per person‑hour but fewer defects, faster long‑term delivery and less knowledge silos. Practical techniques include driver‑navigator, pair TDD and 25‑minute swaps; results include shipping straight to trunk with no pull requests. Current AI assistants (eg Claude) speed generation but act like junior partners, not full replacements.
AI-written summary · about
chapters (17)
- 0:00Introduction and survey
- 1:06About the speaker and Elmax
- 3:13Does pair programming work?
- 4:39Why pair programming works
- 8:10Benefits for teams
- 11:42Long-term advantages
- 15:12Why some developers hate it
- 16:37How to make it work
- 21:35Pair programming culture
- 22:59Pairing techniques
- 26:29When it doesn't work
- 27:53Breaks and intensity
- 31:27Mob programming limits
- 32:52Extreme programming overview
- 34:16AI as a pair programmer?
- 37:03AI's impact on pairing
- 39:31Final thoughts
