Pairing: a guide to fruitful collaboration 🍓🍑🍐
summary
Pairing succeeds when it specifies actions not ideals: require driver and navigator roles, get consent on editor/OS/config, use a dedicated pairing station or separate pairing user, and swap hosts so the typer shares screen — swap screen-share host (Slack screen share or AnyDesk work). Use short timed rotations, narrate intent, favor TDD or ping‑pong to force clarity, resist “let me do this real quick” by unplugging the keyboard if needed, and treat pairing as shared responsibility with instant feedback.
AI-written summary · about
chapters (8)
- 0:00Start
- 10:11Pairing Pitfalls.
- 14:01Pairing needs
- 21:39ready? don't start coding.
- 22:59reach for shared understanding
- 23:33clear expectations
- 24:35consider testing together
- 26:57instead stay on the same page
related talks
47mGlimpses of Humanity: My Game-Building AI Pair
47mGlimpses of Humanity: My Game-Building AI Pair
30mCoding with an Organized Mind
31mInternships: Good for the Intern, Great for the Team
30mTeaching Capybara Testing - An Illustrated Adventure
31mScaling Happy Engineering Teams
17mThe Ruby Environment
25mKeynote – Alex "Skud" Bayley