Apparently It’s Not Called Vibe Coding
Summary
Andrej Karpathy invented the term vibe coding in February 2025. It means you accept every change an AI proposes without reading it. He thought the practice good enough for throwaway weekend projects. But within a year the term meant almost any coding done with AI. The opposite discipline, spec-driven development, sets the design in writing before an AI produces any code. Elizabeth has worked that way since she started working. Each project starts with a map of its modules, database and tests, then a functional specification for every module. The method is heavier, because the developer holds the design and every nuance his their head. But the result can is likely to be more robust than something vibe-coded.
Did you know that if you do vibe coding properly, you are no longer allowed to call it vibe coding? A friend of mine mentioned that he was not suffering any withdrawal symptoms from vibe coding while away on holiday.
I read that and thought, well, lucky him, because I find this whole vibe coding thing exhausting and could do with some time away from it myself. Every day, it expands to consume me.
I said as much to my husband Russell. He let me finish the whole speech about how awful it all was and then said, quite flatly, “You’re suffering because you’re not actually vibe coding.”
Apparently I’m doing spec-driven development (SDD). So I checked.
What is vibe coding?
The phrase was first uttered by Andrej Karpathy, a founding member of OpenAI and formerly director of AI at Tesla, in a now-famous post on X in February 2025. He described a way of working where you “fully give in to the vibes”, forget that the code even exists, accept every change the AI proposes without looking at it, and when something breaks, paste the error message straight back into the chat without comment and just let the AI get on with it.
If the problem will not go away, you keep chatting to the AI, until it does. Karpathy thought it good enough for throwaway weekend projects, things that didn’t matter. He was describing a mood, a vibe, which added up to a certain nonchalance.
What the term meant a year later
But that was what vibe coding meant on the day it was coined. Within a year it had expanded to mean any coding that involved talking to an AI at all. In November 2025, Collins Dictionary made the term “vibe coding” its word of the year. It was defined as using AI, prompted in ordinary language, to help write code.
What I do
Before I open a single build session, I write an overarching specification which I call a map. The map is an overview of a whole project. It lists every module the project is made of, and defines the entire database design, every table and every field. I decide on the module breakdown, the use of third party tools, the database design and the tests. Then I write a funky spec for each module.
The funky spec
Years ago when I worked in software development at Easams in Camberley, I met another graduate, let’s call her Alice, who was also hired as a programmer. The difference between us was that despite having a degree in Maths from Oxford, as yet, she could not code and had to learn on the job.
Bear in mind this was 1983, and in order to write code, I’d design the whole thing at my desk, writing the many lines of pseudo-code down with an actual pen. Next I’d type it into the computer once I had a chance to get on it, translating the pseudo-code into CORAL 66 as I typed.
To get time on the computer you had to book a regular slot and go to a special room. Alice was always in the slot before mine. So I had to help her write her code so that she could finish her work and vacate the room. We did that for months until she started to get the hang of it.
Before we wrote any code we’d have to write the requirements specification and then the functional specifications. Alice would refer to the latter as the funky spec. So today, in memory of those strange times, I still call these things funky specs … the documents that describe what the code must do.
Nothing is decided in the build
Channelling all your thinking into a document first means you dry-run everything in your head. Nothing is decided in the build unless of course you’ve overlooked something.
If a problem does arise mid-build, then I return to the funky spec and amend it. Only then does the coding work resume. Later when testing, any required fixes are reflected in the funky spec so the document stays in line with the code.
So this is SDD
I decide, in writing, the design of the system before Claude builds anything. The AI is doing the coding and I am doing the engineering, and that is called spec-driven development.
It has been the recognised counter-movement to vibe coding for over a year. GitHub built a toolkit around it called Spec Kit and Amazon built an editor around it called Kiro. Anthropic’s own guidance for Claude Code describes similar ideas: explore, plan, code, commit.
I did not learn it from any of them. I arrived at it on my own because I have been writing funky specs since the 1980s.
But it is exhausting
Which brings me back to my friend on holiday. Given a break from all this, I would happily embrace the withdrawal symptoms.
Vibe coding is light because you are not holding all the details in your head. The AI does it for you and sometimes badly. But until something breaks, you experience the incredible lightness of coding.
Spec-driven development is burdensome because you are carrying the design yourself, in your head and then on the page trying to make sure the many .md files Claude needs are all present and correct.
The AI does so much so fast that you get far more done than you could alone. This is he good news. But it also means you are storing more details and balancing more trade-offs in your head – more than we humans were ever designed to balance all day long. When we used to code by hand, the rate of code creation was manageable and you dealth with the burden in smaller, far less chaotic chunks.
That weight is not a problem with the method, rather, it’s the reason my output is a system that can be maintained six months from now. It’s just hard.
But SDD does not sound cool
SDD definitely has a marketing problem. It sounds like a chapter from a dull PRINCE2 manual. Vibe coding sounds funkadelic.
The best names attach themselves to whatever glittering thing the cool kids are doing. I’m pretty sure we all know there is nothing sparkly about writing a specification. It is dull and the temptation is to get Claude to write the whole thing while you never read it. Don’t do that.
So I will go on building from funky specs, exhausted and uncool. Wish me luck.
