Skip to main content

Command Palette

Search for a command to run...

The Mental Tax Nobody's Pricing Into AI-Augmented Engineering

Updated
2 min read
The Mental Tax Nobody's Pricing Into AI-Augmented Engineering

The Mental Tax Nobody's Pricing Into AI-Augmented Engineering

In December, Andrej Karpathy — the guy who coined the term "vibe coding" — posted this:

"I've never felt this much behind as a programmer. The profession is being dramatically refactored as the bits contributed by the programmer are increasingly sparse and between."

Read that again. The inventor of the framing feels left behind by his own framing. He called it a "powerful alien tool... handed around with no manual."

So next time you're watching a teammate prompt Claude like they're pair programming with an old colleague, while you're three rewrites deep on a single function, remember: the most cited AI researcher on Earth is feeling the same thing. It's not a skill issue. It's a profession-wide deep refactor happening in slow motion.

The intervention dilemma is the daily version. Every AI suggestion is a micro-decision: accept, reject, modify, audit. You can't drop into flow because you're playing quality control against a junior dev who codes at superhuman speed and never learns from corrections. A recent fast.ai analysis cited a study where developers thought they were working 20% faster while actually shipping 19% slower. A roughly 40% gap between feeling productive and being productive.

The grief on Hacker News is louder than the productivity numbers. One engineer wrote: "I can't justify writing beautiful hand-crafted artisanal code anymore." Another: "Work now feels duller than dishwater." That's not a tooling complaint. That's a craftsmanship satisfaction loop quietly being severed.

I don't have a fix. Most of what I read about it is either productivity-bro skill-up posturing or vague mindfulness advice, neither of which lands. What I do know: pretending the cost isn't real is making it worse. The teams I respect have stopped optimizing for AI throughput and started naming the tax. AI for boilerplate. Humans for architecture. Permission to ignore the assistant entirely on the work that actually matters.

The skill worth developing in 2026 isn't prompt engineering. It's noticing when the AI is making your day worse and turning it off.