I Have Pair Programmed for 27,000 Hours: Ask Me Anything!
summary
Claim of 27,000 hours of continuous pair programming anchors a laundry list of concrete practices: use Skype and Google Hangouts with screen sharing for remote work but insist both must be able to type to call it pairing, swap drivers frequently with ping-pong pairing and TDD, rotate pairs daily for cross-training, break in when nonverbal cues appear, bring a third person or try both approaches when stuck, accept editor/keymap compromises by using defaults, and schedule solo days or rests to avoid burnout.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:29Overcoming nervousness
- 2:51What is pair programming
- 4:16Benefits and limitations
- 6:01Pair programming without talking
- 7:03Remote pair programming tools
- 8:07Handling disagreements
- 9:34Non-verbal communication
- 12:24Remote vs in-person pairing
- 13:55Pairing with seniors
- 16:22First remote pairing
- 18:07When to work alone
- 19:51Pairing with similar-level developers
- 21:34Different editors in pairing
- 22:59Driving and navigating
- 25:53Balancing rotations and skills
- 28:44Pairing with designers
- 30:12When not to pair
- 31:16Q&A
related talks
40mI've Pair Programmed for 27,000 Hours. Ask Me Anythings!
32mMaximizing the Fun Pair Programming Benefits
34mPair Programming: Better Than Adderall
41mPair Programming
48mPair Programming, TDD and Other Impractical Things
53mHow to really work together as a team
33mSherlock Holmes and Pairing
52mPair Programming: Poop & Pee adventures