# Pair Programming Guide

## Roles
**Driver** — types. Focuses on the current line and immediate syntax.
**Navigator** — reads, thinks ahead, asks questions. Does not type.

Swap roles every 25-30 minutes. Use a timer.

## What the navigator does
- Ask "why" when the approach is unclear. Not to block, to check.
- Note anything that seems wrong but does not need to be fixed right now — say it aloud, write it down, address it after the current task is done.
- Keep the broader goal in view while the driver handles the detail.

## What the navigator does NOT do
- Dictate syntax ("put a semicolon there")
- Take the keyboard without asking
- Check their phone or email

## Session length
Pair for 90 minutes to 2 hours, then take a break.
Pair programming is more mentally intensive than solo work. Do not do it all day.

## When to pair
Good: complex logic, unfamiliar code, debugging, onboarding a new team member.
Not useful: reading documentation, writing boilerplate you both understand, personal admin.

## Common problems
- **One person is dominating**: swap the keyboard now, not in 30 minutes.
- **Big skill gap**: the senior person's job is to ask questions, not give answers.
- **Neither person knows the code**: that's fine — navigating unfamiliar code together is faster than one person doing it alone.