Practice vocabulary for the driver-navigator pair programming pattern: roles, rotation cadence, navigator perspective, catching errors, and implementation focus.
0 / 5 completed
1 / 5
In the driver-navigator pattern, the person who types the actual code into the editor is called:
The driver has the keyboard and types — the driver focuses on the immediate code being written, following the navigator's direction while handling syntax and tooling.
2 / 5
In the driver-navigator pattern, the person who thinks about the broader approach, architecture, and next steps is called:
The navigator sees the big picture and guides — the navigator isn't typing, so they can focus on direction, edge cases, and upcoming challenges rather than the current line of code.
3 / 5
The recommended frequency for switching who has the keyboard during driver-navigator pairing is:
We rotate roles every 15-20 minutes — regular rotation keeps both participants engaged, prevents fatigue, and ensures both people understand the full codebase.
4 / 5
One key benefit of the navigator role is catching small mistakes the driver makes without interrupting their flow. This is described as:
The navigator catches typos and logic errors — because the navigator isn't focused on typing, they naturally spot issues: off-by-one errors, wrong variable names, missing edge cases.
5 / 5
While the navigator handles strategy, the driver's mental focus is described as:
The driver focuses on the immediate implementation — this division of cognitive labor is the core value of driver-navigator: one person executes, one person strategizes.