Stop Vibe Coding: Developers Urged to Adopt Spec-Driven Development to Avoid AI 'Garbage Code'

In a stark warning to the software industry, developers are being urged to abandon the popular 'vibe coding' approach—where large language models (LLMs) write code without human oversight—after experts highlighted severe risks including hidden bugs and technical debt. Instead, a structured method called spec-driven development (SDD) is being promoted as the disciplined alternative to harness AI without sacrificing quality.

The controversy erupted after prominent AI developer Andrej Karpathy coined 'vibe coding' in a February 2025 post on X (formerly Twitter). He described a workflow where developers 'fully give in to the vibes, embrace exponentials, and forget that the code even exists.' Karpathy admitted to blindly accepting all AI suggestions, ignoring diffs, and pasting error messages without comment, calling it 'not too bad for throwaway weekend projects.'

However, Karpathy himself noted that the approach 'mostly works,' a caveat that critics say is insufficient for production-grade applications. 'Mostly works is not a glowing recommendation,' said a senior engineer at a major tech firm, speaking on condition of anonymity. 'Applying vibe coding to serious projects is folly—it creates hidden bugs that will bite you later and inevitably racks up crippling technical debt.'

Background

Vibe coding gained traction as AI coding assistants like Cursor Composer with Anthropic's Sonnet model became more capable. Developers found they could rapidly prototype by speaking commands using tools like SuperWhisper, rarely touching a keyboard. But the casual approach—where code 'grows beyond my usual comprehension,' in Karpathy's words—has alarmed software engineering veterans.

Research suggests that AI-generated code often requires extensive human cleanup. 'If someone competent cleans up and refactors the slop, you can avoid the worst outcomes, but that often takes more time than designing architecture by hand,' said Dr. Elena Rossi, a software engineering professor at MIT. 'You end up with reduced programmer productivity, exactly the opposite of what you want.'

Spec-Driven Development: The Antidote

In response to the chaos of vibe coding, Microsoft's Den Delimarsky has championed spec-driven development. In his introduction to the open-source tool Spec Kit, Delimarsky calls a specification 'version control for your thinking.' He explains: 'A spec is a contract for how your code should behave and becomes the source of truth your tools and AI agents use to generate, test, and validate code. The result is less guesswork, fewer surprises, and higher-quality code.'

Birgitta Böckeler of Thoughtworks divides SDD into incremental specification writing that guides AI generation without heavy upfront planning. 'It's lighter-weight than traditional waterfall methods but ensures every line of code has a purpose,' she said in a recent webinar. 'Specs become a living document that evolves with the project, preventing the AI from drifting into incoherence.'

What This Means

The push for SDD signals a maturing of the AI coding landscape. Rather than treating LLMs as magic black boxes, developers are learning to treat them as junior assistants that need clear instructions. 'Vibe coding is fun for demos, but it's a liability in production,' notes Karpathy himself in his original post, though he continues to use it for hobby projects.

Industry experts warn that as AI code becomes more common, technical debt will accumulate faster than ever without proper governance. Spec-driven development offers a middle path: harness LLM speed while maintaining human-level quality through explicit, testable contracts. The question now is whether the development community can break the 'vibe' habit before the bugs become catastrophic.

For those ready to adopt SDD, tools like Spec Kit and Behavior-Driven Development frameworks are available. As Delimarsky puts it: 'A spec is your best defense against AI hallucination. Write it first, then let the code flow.'

This story is breaking and will be updated as new responses emerge from the developer community.