What is vibe coding?
Vibe coding is building software by telling an AI tool what you want and accepting the code it writes without reading it. Andrej Karpathy named it in a post on X on 2 February 2025. It is great for prototypes and risky for an app that holds user data or takes payments.
Karpathy’s post: “There’s a new kind of coding I call “vibe coding”, where you fully give in to the vibes, embrace exponentials, and forget that the code even exists.” He added that it is “not too bad for throwaway weekend projects”.
Where the term vibe coding came from
Karpathy, a founding engineer at OpenAI and former director of AI at Tesla, described how he was building small web apps with Cursor Composer and accepting every change. In his words, he no longer read the diffs, and the code grew beyond his usual comprehension. He was talking about throwaway weekend projects. That part of the post travelled less well than the name.
The term spread fast. Collins Dictionary made it its word of the year for 2025 and defined it as “the use of artificial intelligence prompted by natural language to assist with the writing of computer code.” That definition is much wider than Karpathy’s. By it, any developer with an AI helper is vibe coding, including the ones who read every line. Many people now use the term for any app built by prompting, whether or not anyone reads the code.
Vibe coding is not the same as coding with AI
Simon Willison drew the line well in March 2025: vibe coding is building software with an AI “without reviewing the code it writes.” If a developer reviews the code, tests it and can explain how it works, that is just software development with an AI helper. Nobody made that one word of the year. The tools can be the same. What differs is whether someone understands what was shipped.
What it builds well
- A clickable prototype to show investors or early users.
- Internal tools used by a few people who trust each other.
- Landing pages, simple forms and dashboards over data you already own.
- A test of whether anyone wants the idea, before you pay for a real build.
Where it breaks
The problems show up in the parts a demo never touches. Nobody demos the password reset. Tools like Lovable and Bolt connect the browser straight to a Supabase database, so the database rules are the only thing keeping one user out of another user’s data. If nobody reads the code, nobody checks those rules.
- Database rules that let any visitor or any logged-in user read every row.
- Secret keys shipped in the front-end code.
- Payments that work in test mode and never update the app in production.
- Login and reset links that still point to a preview URL.
- A fix for one bug that quietly breaks another flow, because there are no tests.
The point where you need a developer
Before strangers sign up, before you take money, and before you store anything personal. At that point someone should read the code and test it as an attacker would. That is what my 14-day Trial does, for $995. I read the repo and the backend by hand, send findings ranked by risk in the first 5 business days, then fix what can be fixed in the 14 days. It ends with a written plan for the rest and a walkthrough call. If you start a monthly plan within 14 days of the Trial ending, the fee is credited to your first month.
If your app is a prototype only you and a few friends will use, you don’t need me yet. Friends report bugs politely. Keep building.