The blank file is dead: how to actually work with AI pair programmers

AI didn't take the job, it took the intimidating empty editor. What's left is the part that was always the real work. Here's how to keep your edge.

The scariest thing in programming used to be the blinking cursor in an empty file. AI mostly killed that — you start with intent and get a confident first draft. That's a genuine gift. It's also a trap if you let it think for you.

The bottleneck moved, it didn't vanish

Generating code was never the hard part. Deciding what to build, catching the subtle bug the model introduced with total confidence, knowing that an abstraction will hurt in six months — that's the job, and AI made it more important, not less. When everyone can generate code, the rare skill is knowing which code deserves to exist.

Habits that keep you sharp

• Read every diff. All of it. If you're merging code you can't explain, you're not the author — you're the rubber stamp.
• Make the AI justify itself. “Why this approach over X?” surfaces the tradeoffs it skipped.
• Build something from scratch on purpose, sometimes — like taking the stairs when there's an elevator. It's how you stay able to judge the elevator.
• Keep the model on a short leash for unfamiliar territory; give it more rope where you can verify fast.

Lean on the tools hard. Just never outsource the taste — that's the only part that was ever really yours.

The engineers who win this era aren't the ones who refuse AI or the ones who blindly trust it. They're the ones who stay good enough to tell when it's wrong.