# Pair Programming in the AI Era

**Author:** Alexey Krivitsky
**Date:** 2026-04-16
**Reading time:** 1 min
**Category:** Org Design
**Tags:** ai, pair-programming, engineering-practices
**Canonical:** https://krivitsky.com/post/pair-programming-in-the-ai-era

---

**TL;DR:** Pair programming is not dead in the AI era. The navigator's job was never reading code line-by-line — it was holding the broader frame: what test is missing, what feature next, do we need this at all. Treat AI-generated code like compiled binary and pair on high-level BDD tests instead.

Pair programming and AI-augmented engineering.

I hear people saying that the practice of pair programming is now dead because no human can read the code at the generation speed. 

I agree. With the fact that one can’t read and understand code so fast. 

But let me offer you a reframing. 

First. The practice of pair programming assumes two distinct roles: navigator and driver. While the driver holds the keyboard and types, the navigator is welcome to read. But mainly the value from the addition pair of eyes and the navigator’s intelligence comes from holding a broader frame. 

What is a missing test?
Which feature do we build next?
Do we need this at all?

These are navigator’s challenges. 

In the AI age? Can still be (and I claim must be) performed by the human. 

And now for the more important reframing. Imagine the old-times pair programming with two humans. One clicks to compile. A binary is produced. The tests are run. Feedback is generated. 

Will the programmers bother to read the binary code?..

Likely not. So why don’t we look at the code that is AI-generated at the speed of light as the binary code and instead focus on high-level tests (like BBD level) that still can be discussed and paired on.