There’s a theory quietly gaining traction among senior developers that cuts against the prevailing panic about AI replacing programmers. Call it the AI skills multiplier — the idea that artificial intelligence doesn’t flatten the playing field between experts and beginners. It widens the gap. Dramatically. And the evidence is starting to pile up in ways that are hard to ignore.
- The AI skills multiplier effect means technically deep developers see the biggest productivity gains from AI tools.
- The AI skills multiplier doesn’t replace expertise — it amplifies it, leaving less experienced coders stuck at MVP stage.
- Animation library author Matt Perry closed 160 GitHub issues in one quarter by pairing deep domain knowledge with AI tooling.
- Anthropomorphising LLMs leads developers to credit the tool rather than the expert wielding it — a costly mistake.
The AI Skills Multiplier Effect Is Real — and the Numbers Show It
Matt Perry knows animations. Not in a “did a few Udemy courses” way — he’s the creator of Motion (formerly Framer Motion), Popmotion, and Motion One, a suite of libraries that collectively underpin animation across a staggering slice of the modern web. His layout projection engine sits in a category occupied by very few engineers on the planet. Perry recently shared that going into 2026 he decided to lean heavily into AI tooling, and what happened next is instructive.
He set a target of closing 60 GitHub issues in Q1. He closed 160. A major refactor of the Motion codebase he’d planned for Q2? Done in a single January afternoon. That’s not a rounding error — that’s a qualitative shift in what one human being can accomplish in a working day. The AI skills multiplier, in action.
It would be tempting to look at those numbers and conclude that the LLM did the heavy lifting. That’s exactly the wrong takeaway. Perry’s results weren’t achieved because Claude or GPT-4 is a better animation engineer than he is. They were achieved because Perry knew precisely what to ask, how to evaluate the output, how to architect around the tool’s weaknesses, and when to override it entirely. Strip away two decades of deep technical expertise and those same AI tools would produce a very different outcome. This is the AI skills multiplier working exactly as it should — rewarding depth, not just access.
What Happens When You Hand AI to a Beginner
For a sharp counterpoint, look no further than Reddit’s r/vibecoding community — a subreddit dedicated to people, mostly without formal development backgrounds, sharing their experiences building with AI-generated code. The stories there follow a predictable arc: initial excitement as a prototype takes shape rapidly, followed by a plateau, followed by a wall. The application works at a surface level but starts fracturing the moment complexity increases.
This isn’t a knock on the people trying. It’s an illustration of what LLMs actually are. These models generate code that satisfies individual prompts. They don’t hold a mental model of your entire application. They don’t reason about long-term architectural consequences. Left without skilled guidance, they patch, accumulate technical debt at alarming speed, and eventually paint themselves — and the developer — into a corner that’s genuinely hard to escape. The codebase becomes a tangled mess that even the AI can’t cleanly fix, because the AI helped create the mess in the first place.
The pattern is consistent enough to be a trend: expert developers are getting dramatically more productive with AI tools, while developers without deep foundations are hitting a ceiling earlier and harder than before. The AI skills multiplier cuts both ways — it accelerates those with strong foundations and exposes those without them far sooner than traditional development ever did.
We’ve Been Overvaluing the Tool, Not the Expert
There’s a very human reason we keep misreading this situation. We anthropomorphise AI systems. When a chatbot explains its reasoning in fluent, confident prose, it’s cognitively difficult to think of it the way you’d think about a hammer or a compiler. We attribute agency to it. We imagine it thinking. And once you’re imagining an autonomous agent, it’s a short leap to imagining it operating without human oversight.
But this is a bias that marketing has exploited for decades in far less sophisticated contexts. Nike didn’t sell Michael Jordan’s sneakers — they sold the implication that the air cushioning technology was the source of his ability to dunk. We bought it because we wanted to believe the tool was the difference. It wasn’t then. It isn’t now.
The Iron Man analogy maps surprisingly well here. Tony Stark’s suit is spectacular technology, but empty it accomplishes nothing useful. The suit amplifies a specific human — one with the engineering knowledge, combat instincts, and strategic judgment to operate it. Hand the suit to someone without that background and you don’t get Iron Man. You get a very expensive disaster. If Perry handed over the keys to the Motion repository tomorrow and someone without his depth tried to match his AI-assisted output, the codebase would be broken within weeks. Understanding the AI skills multiplier means understanding that the suit is only as good as the person inside it.
What This Means for Developers Learning Right Now
The practical implication for anyone learning to code, or wondering whether to deepen existing skills, is actually more reassuring than the current discourse suggests. Technical depth is not becoming less valuable — it’s becoming more valuable. The AI skills multiplier means that every additional hour you invest in genuinely understanding systems, architecture, and domain-specific knowledge pays out more now than it did five years ago, not less.
This does create an uncomfortable tension, though. The tools that are easiest to demo — the ones that spin up a working prototype from a plain-English prompt — make it look like foundation-level knowledge is optional. It isn’t. It’s just deferred. The gap between a working demo and a production-ready, maintainable application is where expertise lives, and AI hasn’t closed that gap. If anything, by making the early stages faster and more accessible, it’s made the later stages more demanding.
This also has implications for how teams should think about hiring and upskilling. A mid-level developer with genuinely deep knowledge in a specific domain will likely outperform a senior developer with broad but shallow skills in an AI-augmented workflow, because the AI skills multiplier has more to work with. Depth compounds.
The Skills That Actually Compound With AI
What kinds of knowledge feed the AI skills multiplier most effectively? A few patterns stand out from watching how high-performing developers actually work with these tools:
- Architectural intuition — knowing when the AI’s suggested structure will cause problems six months from now, even when it looks clean today.
- Domain-specific mental models — like Perry’s understanding of layout projection, physics simulations, or delta time. AI can generate code in these areas, but only someone who understands the underlying concepts can validate it.
- Debugging literacy — the ability to read AI-generated code critically, spot the subtle errors, and understand why something fails rather than just asking the AI to try again.
- Systems thinking — understanding how individual components interact across an entire application, something LLMs demonstrably struggle to maintain across long, complex sessions.
None of these are skills you develop by prompting an AI. They come from building things, breaking them, reading other people’s code, and accumulating the kind of pattern recognition that only time and deliberate practice creates. There’s no shortcut, and the AI tools themselves are not the shortcut.
The Bigger Picture for the Industry
The AI skills multiplier framing matters beyond individual career decisions. It has implications for how companies staff engineering teams, how bootcamps and computer science programs should structure curricula, and how the broader industry thinks about the relationship between AI tooling and human expertise.
The current narrative — that AI will eventually replace developers entirely — tends to assume that the gap between AI-assisted expert output and raw AI output will close as models improve. Maybe it will. But the history of software tooling doesn’t strongly support that prediction. Every major productivity tool — from IDEs to version control to cloud infrastructure — amplified skilled developers far more than it democratised access to their outputs. The tools got better. The experts got faster. The gap persisted.
The developers who will thrive in an AI-saturated environment aren’t the ones who’ve outsourced their thinking to the model. They’re the ones who’ve built enough genuine understanding that the model becomes an extraordinarily powerful extension of what they already know. That’s the AI skills multiplier — and right now, it’s one of the most important concepts in software development that almost no one is talking about clearly enough.
Source: https://www.joshwcomeau.com/email/wham-launch-005-elephant-2-p/
