The Pair-Programming Flow

In classical pair programming, one person types (driver) and one thinks (navigator). With the agent, you're the navigator. Your job is shape, intent, and quality — not characters.

The pattern: state intent in 2-3 sentences. Watch the agent act. Read the diff. Approve, redirect, or correct. Don't context-switch back to writing characters yourself; if something's wrong, *say what's wrong* and let the agent fix it.

Two skills compound here. First, learn to articulate intent precisely — vague prompts produce vague code. Second, learn to read diffs faster than you can write them. That's where the speedup actually lives.