Why AI Isn’t Replacing Developers – It’s Amplifying Skill

The conversation around generative AI has settled into a familiar pattern: headlines proclaim that code‑writing bots will soon make human developers obsolete. In a recent newsletter, Josh W. Comeau pushes back, pointing out a more nuanced reality. AI models are undeniably good at generating snippets, fixing bugs, and even refactoring large codebases, but the real story is how those abilities intersect with a developer’s existing expertise.

---

The evidence: productivity spikes for the already‑skilled

Comeau cites Matt Perry, the creator of animation libraries such as Popmotion, Motion One, and the former Framer Motion. Perry used an LLM to close 160 issues in Q1 2026—more than double his target—and to refactor a major library in a single afternoon. For someone who already understands the intricacies of layout projection engines, the AI acted as a force multiplier, handling boilerplate and suggesting optimisations that would have taken hours to write by hand.

This pattern repeats across the community: senior engineers report AI‑driven speed‑ups of 2‑3× on routine tasks, while still needing to review, test, and integrate the output. The tool works best when the developer can:

1. Formulate precise prompts – knowing the right terminology and constraints.
2. Validate generated code – spotting logical flaws or performance regressions.
3. Guide the model toward architectural goals – steering the conversation rather than accepting a single answer.

The counter‑perspective: novices hit a wall

On the flip side, Comeau highlights the /r/vibecoding subreddit, where newcomers share stories of LLMs “painting themselves into a corner.” Without a solid mental model of software architecture, the model’s suggestions often become tangled, leading to fragile MVPs that can’t scale.

Key pain points for less‑experienced users include:

• Missing context – the model can’t infer project‑wide constraints that a seasoned dev would know.
• Over‑reliance on surface‑level fixes – developers may accept a generated solution without understanding why it works (or fails).
• Fragmented codebases – repeated prompts can produce inconsistent styles, making maintenance a nightmare.

These issues illustrate a broader cognitive bias: we tend to overestimate the power of a tool when we see spectacular results from a few experts, then assume the same outcomes are universal.

Re‑framing AI as a “suit” rather than a “replacement”

Comeau likens LLMs to Iron Man’s suit: powerful, but only when worn by someone who already knows how to fly. The suit doesn’t teach you to pilot a jet; it augments the pilot’s existing skill set. Similarly, an LLM can:

• Generate boilerplate (e.g., component scaffolding, type definitions).
• Suggest algorithmic alternatives (e.g., swapping a naïve loop for a more efficient map/reduce).
• Provide quick documentation look‑ups (e.g., summarising a Web API).

But it won’t replace the need for:

• Domain knowledge – understanding animation physics, accessibility standards, or performance budgets.
• Design thinking – deciding what to build, not just how to code it.
• Critical review – testing, profiling, and refactoring the AI’s output.

What this means for career planning

1. Invest in fundamentals – mastering JavaScript, TypeScript, and core web concepts will pay off more than chasing the newest AI plugin.
2. Learn to prompt effectively – treat prompt engineering as a skill: concise, context‑rich, and iterative.
3. Adopt a review‑first workflow – run AI‑generated code through linting, unit tests, and code reviews before merging.
4. Focus on higher‑level problems – architecture, system design, and user experience remain human‑centric challenges.

Counter‑arguments and open questions

Some argue that AI will eventually internalise enough context to handle architecture autonomously. Projects like GitHub Copilot X and Google DeepMind AlphaCode are moving toward more holistic code generation, but they still rely on large, well‑documented codebases and extensive training data. The gap between generating a function and orchestrating a multi‑service micro‑architecture remains substantial.

Another concern is the environmental cost of training ever‑larger models. While the productivity gains are real, the carbon footprint of continuous model iteration raises ethical questions that the community has yet to address comprehensively.

---

Bottom line

AI is reshaping daily developer workflows, but it is not a wholesale replacement for human expertise. The technology amplifies skill—those who already understand the craft see dramatic speed‑ups, while those still building foundational knowledge may find the tools confusing or even counter‑productive. The most sustainable path forward is to treat LLMs as sophisticated assistants, not autonomous creators, and to double down on learning the concepts that make those assistants useful.

What’s your experience with AI‑assisted coding? Are you seeing a productivity boost, or are you hitting the “paint‑the‑corner” problem? Share your thoughts in the comments.