A vibe coder describes an app to an AI tool and ships what comes out, without an engineering background behind it. I use the same kind of tools, so speed is not what separates us.
What you get
Someone with no engineering background, or you yourself, describing an app to an AI tool and shipping what comes out. The first version can appear in an afternoon, and it can look finished.
What you do not get is anyone who can tell you whether it is finished. The tool will say that it is.
Where this route is right
For a demo, a landing page or an idea you want to try on real people this week, this is the right call. Nobody should pay a senior developer to find out whether anyone wants the thing.
If it works, you will know what to build properly, and you will have spent very little to learn it.
Where I am different
The difference is what happens after the agent says it is done. I read the code, run the real flow as a real user, check the security rules and look at what the database allows. A demo and a product look the same until someone signs in with the wrong account, a quota runs out or the store reviewer writes back.
A green build is not evidence that a feature works. The first two days of rebuilding this site, below, are the example I would point at: eight defects that the automated checks had passed.
That review is the slow part, and it stays with me. Agents made the writing fast; they did not make the checking fast.
What you can check
My side of this rests on the products below. Each one opens, and each date comes from its commit history or my own project records.