AI Ate the Tactical Side of Coding, So Every Developer Is Now a Lead

When AI takes over the low-effort mechanical parts of programming, what remains is nonstop strategic thinking, and that is why AI coding leaves people drained. This is a short talking-head clip from Matt Pocock, the TypeScript educator behind AIhero.dev. He sits at his desk with a podcast microphone and makes a single argument about why so many developers feel tired after a day of working with AI tools.

The Tactical Break Is Gone

Pocock's central claim is that coding used to include a kind of rest. He describes older coding sessions as "a little break for your brain," the tactical side where you are "on the ground" doing "almost nonverbal reasoning," moving stuff around, "kind of playing a game almost." That low-effort flow state was part of the work, and it gave the mind somewhere to coast.

His point is that AI has removed that layer entirely. "All AI has just eaten that," he says. "AI has eaten the tactical side of programming." The mechanical typing and small-scale problem solving that once padded out a work session is now handled by the tool, so it no longer exists as a place to relax.

Everyone Got Promoted to Lead Developer

With the tactical work gone, Pocock argues that everything left is strategic. Developers now have to "operate at a level above the AI" and "think above the level that the AI is operating at." His framing is that "we've all turned into lead developers." We have moved higher up the chain, and that position demands high-level thinking all day.

This is the core of why the work feels heavier. A lead developer role has always been more mentally taxing than heads-down coding, because it is planning, direction, and judgment rather than execution. Pocock's observation is that AI pushed the whole profession into that role without anyone choosing it. He is candid that he does not have a fix: "I don't honestly know what we do about this. I think it's just baked into the loaf."

The Same Shift Applies Beyond Code

Pocock extends the point past programming. Anyone using AI, "whether they're using it for coding or anything else," is having their "boring grunt work taken away," which means "their brain is under so much more strain." The trade is the same in any field: the tool absorbs the easy tasks and leaves the person with only the hard decisions.

The whole clip is delivered straight to camera in a plain home-office setting, a bookshelf and wooden furniture behind him, which keeps the focus on the argument rather than any demo. There is no code or tool walkthrough on screen. It is an observation, not a tutorial.

Enjoyable and Exhausting Are Not Opposites

The clip ends on a nuance that keeps it from being a complaint. Pocock says he actually likes the change. "I do like making high-level decisions," he says, "but I end each day pretty knackered." That is the honest takeaway. The work can be more interesting and more tiring at the same time, and both things being true is exactly why the exhaustion catches people off guard.

Key Takeaways

• Older coding sessions included low-effort tactical work that functioned as mental rest, and AI has removed that layer.
• With the mechanical work automated, the remaining work is almost entirely strategic and long-term thinking.
• Pocock argues that AI has effectively promoted every developer into a lead developer role, which is inherently more draining.
• The same pattern applies to any AI-assisted work, not just coding: grunt work leaves and high-strain decisions remain.
• Pocock has no proposed solution and treats the mental strain as an unavoidable feature of the new workflow.
• The shift can be genuinely enjoyable and genuinely exhausting at once, which is why the tiredness surprises people.

Resources

• AIhero.dev — Matt Pocock's platform for learning to build with AI.
• Matt Pocock on X — his ongoing commentary on TypeScript and AI development.
• Total TypeScript — Pocock's TypeScript course platform.