AI Pair Programming

AI pair programming is working collaboratively with an AI in real-time on a codebase, where the AI can read, write, and modify code within the context of your actual project. It follows the classic pair programming model: you play the navigator (setting direction, making design decisions, reviewing output) while the AI plays the driver (writing code, suggesting approaches, catching errors). The combination of your domain knowledge and the AI’s technical breadth produces better results than either working alone.

The Simple Version

Pair programming is an old idea from software development. Two people sit at one computer. One writes the code (the “driver”), the other reviews it in real-time and thinks about the bigger picture (the “navigator”). It catches bugs faster, produces better designs, and keeps both people sharp.

AI pair programming is the same concept, but your partner is an AI. You describe what you want to build. The AI writes the code, suggests approaches, catches potential problems, and handles the implementation details. You stay in the navigator seat: setting goals, reviewing output, making architectural decisions, and steering the direction.

Why It Matters

Traditional pair programming requires two developers with compatible schedules and skill levels. AI pair programming is available anytime, infinitely patient, and can work across any programming language or framework. For non-developers, it lowers the barrier to building real software from “learn to code” to “learn to describe what you want clearly.”

The key difference from simply asking an AI to generate code: pair programming is iterative and collaborative. You’re not firing off a prompt and accepting whatever comes back. You’re working together, round by round, with the AI building and you reviewing, adjusting, and directing.

This is different from vibe coding in an important way. Vibe coding is about momentum and speed, describing what you want and letting the AI run. AI pair programming adds a layer of deliberate review and architectural thinking. You’re still moving fast, but you’re also making sure the foundations are solid.

How It’s Used on This Site

Every feature on this site was built through AI pair programming. Scott describes what he wants, Claude Code builds it, Scott reviews the output in Cursor, and they iterate until it’s right. The process is visible in the blog posts: each one documents what was built, how decisions were made, and what the collaboration actually looked like. The PLAN.md and CLAUDE.md files make this partnership more effective by giving Claude Code persistent context about the project’s goals and conventions.