There were stories of people validating their idea using 'no code' i.e. building a very crude version of their startup quickly, and deeming 'no code' very useful because the benefits of fast idea validation outweighed the downsides of 'no code' (e.g. inextensible design, UX deficiencies, 'toy app' feel etc).
Fast forward to today, there's a lot of hype around 'vibe coding', which can make existing devs more efficient. But have there been any cases of someone who couldn't previously code being able to make a successful start up by way of 'vibe coding', if so, who/what?
Once your codebase reaches the size needed to solve actual business problems, the quality of the output varies wildly, the complexity of the prompts required to produce useful code increases, and the output code requires significant editing to actually integrate without bugs or errors.
My personal opinion is that for vibe coding to be viable as the complexity of feature requirements or the size of the code base increase, the specificity and complexity of the input prompt will eventually demand more from the engineer than just writing the code, since code is more specific by definition than natural language.
I've also seen incidents of those apps turning out to have security holes you can drive a truck through, and hiring professional help to move beyond their origins.
(I didn't keep notes of the companies and I don't want to specifically call any out, but they exist.)
I'm hoping this is a relatively short-lived trend. I think vibe coding tools for personal use and prototypes is to be celebrated, but vibe coding software that other people will depend on or even pay for is deeply irresponsible.
I've made a couple of things lately that I sometimes tell people are "vibe coded" because they were heavily facilitated by LLMs, but it's not really true in the pure, literal sense.
And they usually try to sell you their courses/mentorships.
I don't know if I'm being suspicious because they seem fake or because they came out of nowhere and are earning in a month what I make in a year.
I've been using VSCode's Copilot with Claude Sonnet 4 and find it to be terrifyingly competent running 8 hours a day costing ~$10.
I am developing techniques to keep it moving forward producing code and fast. First, prompt engineering like "write clean, simple, and elegant code." Second, I use TypeScript script very strictly which helps. Third, the models are amazing at producing very simple test units which will be important in the fifth. Fourth, I use techniques like "look for opportunities to refactor pure functions in the file and put them at the top of file" or "look for opportunities to refactor pure function and put them in shared utils.ts file." Fifth, every hour or so, I will have the agent simplify and clean the code and with complete test coverage both unit and integration as longs as they all pass .... good to go.
This is a process and it is the same every time. So now I'm thinking about how do I write code to automate these steps into an automated process. For example, I keep using the same pattern of steps to solve hard debugging problems which I'm going to leave out of this conversation now. If I can create a process in code, I'd be one step closer to complete automation coding.
The patterns are emerging. I strongly believe in 12 months these systems are going to be able to write extremely complicated programs with very little input from the human in the loop.
If it's a non-programmer trying to build a non-trivial software product with AI I haven't heard of anyone successfully doing that and I'm very confident in saying theres no chance it'll happen with todays AI