Pair Programming Doesn't Suck Anymore

Classic pair programming could get weird fast. One person drove, one person watched, and sooner or later somebody felt judged or sidelined.

What changed for Aaron and me was simple: the AI does the typing.

Now the two of us stay on the parts that actually need humans. One pushes direction. One pushes back. We debate architecture, tradeoffs, naming, scope, and risk. While we do that, the AI turns the conversation into code, tests, and file edits.

That setup kills most of the bad vibes. Nobody is defending their typing speed. Nobody is hovering over someone else's shoulder waiting for the keyboard. The AI absorbs endless correction without ego, so we can be blunt, fast, and specific without turning the session into interpersonal friction.

It also changes pacing. If one of us has a half-formed idea, we can throw it at the AI, see the concrete draft, and react to something real. The conversation moves from "I think maybe..." to "here's the diff; keep this part, delete that part."

The solo version works the same way. Building the VTuber project, I'd argue with Claude about transparency layers — the avatar kept rendering as a flat image wiggling on screen instead of a composited character with proper alpha blending — and the back-and-forth had the same rhythm as a good pairing session. I pushed direction, Claude typed, I corrected, Claude adjusted. The difference is that there was no second human to sanity-check my judgment. That's the tradeoff: solo pair-programming with AI is faster but lonelier. You get all the mechanical leverage and none of the "are you sure about that?" from someone who isn't trying to please you.

The lesson is practical: keep humans on judgment and keep AI on mechanics. Pair programming starts working when both people can think together instead of perform for each other. And if there's only one person, the thinking still has to happen — you just have to be more honest with yourself.