~/talk

The developers worked in two by two. Hurrah! Hurrah!

links:none on file
slides:none on file

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

  1. 0:00Introduction and survey
  2. 1:06About the speaker and Elmax
  3. 3:13Does pair programming work?
  4. 4:39Why pair programming works
  5. 8:10Benefits for teams
  6. 11:42Long-term advantages
  7. 15:12Why some developers hate it
  8. 16:37How to make it work
  9. 21:35Pair programming culture
  10. 22:59Pairing techniques
  11. 26:29When it doesn't work
  12. 27:53Breaks and intensity
  13. 31:27Mob programming limits
  14. 32:52Extreme programming overview
  15. 34:16AI as a pair programmer?
  16. 37:03AI's impact on pairing
  17. 39:31Final thoughts
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.