Recipe
Pair programming session structure guide
A repeatable 60-minute template for effective pairing sessions that ship code.
Ingredients
- Two engineers, one workstation
- Shared branch with a single well-scoped ticket
- Timer set to 25-minute intervals
- Scratch file for notes and design decisions
Session flow
0:00–0:05 — Align
Read the ticket aloud. Agree on the acceptance criteria and the first concrete step. Driver shares screen.
0:05–0:25 — Sprint 1
Driver writes, navigator thinks one step ahead. Navigator catches edge cases and suggests refactors. No silent periods longer than 90 seconds.
0:25–0:30 — Pivot
Swap roles. Navigator becomes driver. Quick verbal handoff of current state and next intent.
0:30–0:50 — Sprint 2
New driver continues. Focus on finishing the implementation or reaching a clean checkpoint.
0:50–0:60 — Retro
Commit or stash. Both engineers write one thing that worked and one thing to improve next session.
Anti-patterns
- Navigator checking Slack or phone
- Driver ignoring navigator input for more than two turns
- Skipping the retro because “we’re good”
- Pairing on a ticket too large for one session
Adapted from Meridian engineering rituals. Revisit this recipe before every pairing session until the rhythm becomes automatic.