You're Not the Engineer Anymore. You're the Director.

Andrej Karpathy hasn't typed a line of code since December.

He spends his days "expressing his will to agents." He feels nervous when he has subscription tokens left over — the way he used to feel when his PhD GPUs weren't running.

I keep thinking about what that actually means for people who build software for a living.

For 30 years, the constraint was execution. You had the idea in seconds. You spent three days implementing it. The bottleneck was always the gap between what you could think and how fast you could build.

That bottleneck is gone.

Which means the thing that was always the scarce resource — the vision, the judgment, the ability to know what to build and why — is now the only resource that matters. The implementation follows.

Grove called it leverage. A manager's output equals the output of their organization. The best engineers I worked with at Google weren't the fastest coders. They were the ones who could look at a system, understand its failure modes before they happened, and make everyone around them smarter. That judgment compounded through the team.

Now it compounds through agents.

The teams I'm seeing pull ahead aren't the ones with the best AI tools. They're the ones who figured out that waiting is waste. Every idle moment is an agent that could be running. They've stopped thinking about what they can do and started thinking about what they can direct.

That's a different skill. Most engineers haven't made the switch yet. Most organizations haven't realized they need to hire for it.

You're not the engineer anymore. You're the director.