Pair Programming Vocabulary | Pair Programming Exercises

1 / 5

In pair programming, one person is the "driver" and the other is the "navigator".

What is the driver's role?

The driver/navigator split separates tactical execution from strategic thinking:

Role	Focus	Typical activities
Driver	Tactical — hands on keyboard	Typing, syntax, immediate implementation details
Navigator	Strategic — watching the big picture	Catching errors, researching, thinking about next steps, edge cases

Regular role swaps (every 10–20 minutes) prevent fatigue and keep both participants engaged. Key vocabulary: "driver/navigator roles", "role swap", "tactical vs. strategic focus".

2 / 5

Your pair partner finishes their turn and says "Want to take the keyboard?"

Which response best handles this role handoff?

A good role handoff verifies shared context before the new driver starts writing code:

Response	Problem
A — "Give me a moment"	Passive — doesn't engage with the context, creates awkward pause
B — "The keyboard is yours"	Wrong direction — this is what the partner already said
C — "I'll be the navigator now"	Contradicts the handoff — reverses who is driving
D ✓ — Recap + confirm next step	Confirms shared understanding, prevents duplication or wrong direction

Key vocabulary: "handoff", "recap current state", "what's next", "pairing session continuity".

3 / 5

During a pairing session, your partner writes a piece of code you don't understand.

Which response is most appropriate for a beginner navigator?

The navigator's responsibility is to understand and guide — asking questions in real time is a core obligation, not an interruption:

Response	Why it fails
Staying silent	Navigator cannot guide if they don't understand — defeats the purpose of pairing
Taking the keyboard unilaterally	Skips learning; causes confusion; breaks the pairing dynamic
Googling privately	Separates the session; partner loses awareness of the confusion

Useful pairing vocabulary: "can you explain", "help me understand", "walk me through", "so if I'm following, this… is that right?"

4 / 5

At the start of a pairing session, your partner asks: "Should we timebox this?"

What does "timebox" mean in a pairing context?

Timeboxing in pairing prevents two common failure modes:

Failure mode	How timeboxing helps
Rabbit hole — spending hours on one approach	"15 minutes — if no traction, switch approach"
Open-ended investigation that never ends	"30-minute spike — then decide based on what we know"

Key vocabulary: "timebox", "set a timer", "re-evaluate at N minutes", "pairing goals for this session", "anti-yak-shaving".

5 / 5

"Let's do a quick navigator check-in."

What does a navigator check-in accomplish during a long pairing session?

Navigator check-ins maintain strategic alignment during long driving periods:

Check-in type	Example phrasing
Direction check	"I notice we've been on this for 30 minutes — should we step back and reconsider the approach?"
Edge case flag	"I think there's an edge case we haven't handled yet — what if the user list is empty?"
Energy check	"Should we swap roles? I've been navigating for a while."

Key vocabulary: "navigator check-in", "course correction", "stepping back", "strategic pause".