What Happened
Jeremy Howard, co-founder of fast.ai and Answer.AI, published a video titled "The Dangerous Illusion of AI Coding?" that landed on Hacker News on March 7, 2026. The video extends arguments Howard has been building for months, most notably in his January 2026 essay "Breaking the Spell of Vibe Coding" and a podcast appearance where he called vibe coding "a slot machine."
Howard's central claim is blunt: "People who go all in on AI agents now are guaranteeing their obsolescence. If you outsource all your thinking to computers, you stop upskilling, learning, and becoming more competent."
His specific critiques target the gap between what AI coding tools produce and what production software actually requires. AI can generate syntactically correct code, he argues, but it cannot produce meaningful abstractions, proper modularization, or sound architectural decisions. The code compiles. It might even run. But it lacks the judgment that separates a working prototype from maintainable software.
Howard's proposed antidote is his "Solve It With Code" course, built around iterative problem-solving with small steps, deep understanding, and reflection. He describes it as "basically the opposite of vibe coding."
Why It Matters
This isn't a random critic shouting into the void. Howard is one of the most respected figures in practical deep learning education. When he says AI coding tools create an "illusion of competence," that carries weight with the developer community.
The timing matters too. We're in a period where AI coding assistants are the fastest-growing category in developer tools. Cursor crossed a million users. Claude Code ships as a standalone product. GitHub Copilot is embedded in most professional workflows. The pressure to adopt is real, and so is the pressure to stop learning fundamentals.
For developers using these tools daily, Howard's argument poses a practical question: are you using AI to amplify skills you already have, or are you using it to skip learning skills you don't? The answer determines whether you become more capable or more dependent.
Our Take
Howard is right about the risk, but the framing is too binary. The slot machine metaphor works for pure vibe coding, where someone types a prompt and ships whatever comes back. That approach is genuinely reckless for anything beyond prototypes.
But the best practitioners we've seen use AI coding tools differently. They treat Cursor, Claude Code, and Aider as accelerators for tasks they already understand. They review every diff. They refactor the AI's output. They use the time savings to tackle harder problems, not to stop thinking.
The real danger isn't AI coding tools themselves. It's the narrative that you don't need to understand code anymore. Howard is fighting that narrative, and he should be. Junior developers who skip fundamentals because "AI will handle it" are building careers on sand.
If you're using AI coding tools, pressure-test yourself: could you write this code without the tool? If yes, keep going. If not, that's your signal to learn, not to prompt harder.