Ping Ping or: How I learned to stop worrying and love remote paring
summary
Remote pairing succeeds when setup is fast, access is equal and communication is disciplined: use Google Hangouts or FaceTime for video, Logitech H930 or Blue Snowball for clear audio, share a tmux session or Cloud9/Matey URL so both can edit, or VNC/NoMachine for remote hosting; Screenhero is promising. Enforce share everything, limit debates to five minutes, take breaks (stand up or pee), send a pre-session setup email, and rely on synergies like pair negotiation and continuous review to reduce bus factor and raise code quality.
AI-written summary · about
chapters (16)
- 0:00Introduction about the speaker
- 0:36What is pair programming
- 2:22Remote pair programming basics
- 4:30Ground rules for remote pairing
- 7:21Synergies in pair programming
- 10:35Habits of good pair programmers
- 11:15Establishing pairing flow
- 12:19Recommended audio tools
- 13:24Tools for remote pairing
- 17:47Web platform editors
- 19:15Screen sharing options
- 21:00IDE-based pairing solutions
- 22:06Finding remote pairing partners
- 23:34Q&A about pairing tools
- 24:46Expert-novice pairing dynamics
- 26:32Who should not pair program
related talks
57mRemote Pairing
48m(Remote) Pair programming
28mProblem Solving Through Pair Programming
01h 01mPairing, Sharing, Caring - One team's journey to Pair Programming
35mPair Programming from 2,000 km Away: Strategies for Distributed Agile Teams
41mto-Peer PowerShell: The Ins and Outs of Pair Programming
32mMaximizing the Fun Pair Programming Benefits
47mPanel: The Culture of Hybrid Work