Vibe Coding Is the Worst Idea of 2025 [video]
Key topics
The video 'Vibe Coding Is the Worst Idea of 2025' sparks a debate on the merits and drawbacks of Vibe Coding, with some users praising its potential for rapid prototyping and others criticizing its limitations and potential security risks.
Snapshot generated from the HN discussion
Discussion Activity
Very active discussionFirst comment
45m
Peak period
64
0-6h
Avg / period
13.8
Based on 83 loaded comments
Key moments
- 01Story posted
Aug 20, 2025 at 2:02 AM EDT
5 months ago
Step 01 - 02First comment
Aug 20, 2025 at 2:47 AM EDT
45m after posting
Step 02 - 03Peak activity
64 comments in 0-6h
Hottest window of the conversation
Step 03 - 04Latest activity
Aug 23, 2025 at 4:21 PM EDT
4 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
Step 1: Some upstarts create a new way of doing something. It’s clunky and unrefined.
Step 2: "Experts" and senior folks in the field dismiss it as a "toy." It doesn't follow their established rules or best practices and seems amateurish. They wouldn't recommend it to anyone serious.
Step 3: The "toy" gets adopted by a small group of outsiders or newcomers who aren't burdened by the "right way" of doing things. They play with it, improve it, and find new applications for it.
Step 4: The "toy" becomes so effective and widespread that it becomes the new standard. The original experts are left looking out of touch, their deep knowledge now irrelevant to the new way of doing things.
We're at step 2, bordering on 3.
* Executives at Nokia and BlackBerry saw the first iPhone, with its lack of a physical keyboard, as an impractical toy for media consumption, not a serious work device.
* Professional photographers viewed the first low-resolution digital cameras as flimsy gadgets, only for them to completely decimate the film industry.
Good time saver though, if you do.
Splitting tasks into small verifiable chunks that can be completed in a reasonable time frame (Context window).
Smart people get things wrong all the time. But that isnt to say we jump at every opportunity.
The problem is that the experts have tried it and found that vibe coding doesn't actually work at scale that they need.
Will it ever? Perhaps, but I'd argue a near-AGI level of intelligence would need to be achieved first. When that happens, we have bigger problems (and/or opportunities?) than a few programmers losing their jobs.
Eventually it will spit out something that works. Sometimes it gets very stuck and you have to delete everything it did and start again.
Yes, you can't vibe code a full-ass enterprise level product fit to sell as SaaS for a Fortune 500 company.
But what you can vibe code is a bunch of small _bespoke_ tools that fit your exact use-case. Stuff you could buy (or rent) as SaaS, but they'd have 80% too many features and a constant monthly cost.
Just last week I converted a bunch of docker compose -based containers to run on Opentofu, took me maybe an hour or two with Claude Code while watching TV.
Would've been a week easy if I went for the artisanal route of reading Terraform documentation and digging through forums and Stack Overflow.
Not a world-changing thing, I could've lived with the compose setup, but now the whole system is declarative. I set the state and the state is applied, no drift.
The real problem with it is that it doesn't work. It isn't "right way wrong way". It doesn't work.
EDIT: digital cameras didnt work, until it did. streaming didnt work, until it did. ecommerce didnt work, until it did.
Supersonic passenger flights did work until they didn't.
And many more innovations which are not viable.
What?
But this is still largely true.
NFTs and Web3 were a VC and hype powered rug-pull from the beginning.
LLMs on the other hand can solve problems. Not every problem, not perfectly. But you can solve actual things with them today.
Is there hype? Fuck yes there is. So much hype and snake oil. But there's a nugget of actual usefulness hidden in there.
If you're building "production ready" stuff with logins for Other People and god forbid taking payments, yes you definitely must understand what the code does.
But when I'm building a tool that tags random meme reaction .webm files and finds duplicates from them, I couldn't care less what the quality is or if I understand what it does.
I can easily run it, observe if it does what I want and Vibe harder if it doesn't.
tl;dr vibing prod code = bad. vibing personal tools = good.
Step 3 only occurs in a small fraction of cases. Step 4 even smaller fraction.
And it only takes one or two breakout products to create a buzz around a platform or method in our world nowadays.
People are so invested in this bubble they have to believe it will not burst at all costs.
If this works as well as the evangelists say, they'll all soon be millionaires, right? Everyone is 10x more productive! I'll be waiting... seated.
The good part about this is that if it does indeed get as good as they claim, anyone will be able to get the same benefits. If it doesn't, I'll be around to fix all the garbage code vomited out of LLMs.
If this works—even remotely—this will devastate upcoming entry level software engineering vocations and no longer will we have an army of bright people choosing that vocation. You will still need the upper class SWEs to manage and refine what the AI produces. However at that point AI will need to improve beyond the need for the upper class because you have dried up your engineering well. So what I see is an eventual technological stagnation…or shitification brought about by AI.
It's likely not only in tech, even. We see how blatantly students are getting their degrees and bragging about having ChatGPT do all of their assignments. These folks won't start their careers and suddenly study to get good at their jobs, they'll only function if they have these tools. This is the master move from the AI pushers. They've successfully created a real dependency for millions.
Imagine the next generation of doctors that don't know anything about medicine without ChatGPT at their side. What a nightmare.
You say that like subsequent events overtook them. But I see this complaint on HN pretty frequently. I agree with it. Nobody does their work on a phone. The phones go out of their way to make that difficult.
I don't think you could be less in touch with the current business world.
This also is how most people use their smart phone today. They were right. Perhaps they just didn't realize that people wanted a on-the-go impractical toy for media consumption.
But Nokia had released a touchscreen phone even before the iPhone and their first iPhone-like smartphone was in 2008 so only a year after the first iPhone. What they stuck with for too long is Symbian, which was blown out of the water by the iPhoneOS and then its apps ecosystem. In contrast, Samsung quickly ditched Symbian what whatever else they were using to adopt Android.
The "burden" in this case is correct, secure, as much bug free as possible code that someone can debug.
You oversimplify everything, but this is completely wrong. 320P cameras were useless to pro photographers, but as soon as the capabilities got near to what film could provide, they eagerly switched. Kodak was destroyed, but there wasn't much of a place to pivot to. "Masters of a complex, chemical domain" to "Yet another camera company" isn't a real pivot.
I'm bullish on AI, and think "vibe" coding was/is a cool experiment so don't agree with the premise that it is in the worst idea, but strongly disagree with your simplistic take on how tech is adopted. There are countless ideas that "experts" were right to ignore, ideas sitting in the trash can of history.
Now this, and I also vibe code but I'm not convinced it will change too much for the coding profession. Will probably make it suck a bit more in relation to management and juniors who will make more laziness mistakes quicker.
His insight was that in some cases, there can be a product that's worst in every way than a product a company is currently producing. Every way, except one. And that one way is not interesting to the company's customers, so the company almost categorically can't care about it. But that one improvement ends up being massive, usually because it unlocks a new product category that brings in new customers.
For example, think of the massive computers of the early era (and allow me some small liberties in this story). The only things that mattered were strength/speed and cost. But then much smaller versions of computers became available. Originally for hobbyists. No company that built computers cared about this development, because none of their customers cared! These computers were inferior in every way current customers cared about, and were only better for a tiny group of people who weren't customers and no one cared about.
But obviously, home computing ended up a much bigger deal than anything else, and eventually because it was so massive, improvements there led to improvements for the original customers.
That is the dilemma. Do you ignore existing customers who are perfectly happy with what you're building, to chase an illusive innovative growth in a new segment of the market which you have no idea will materialize or not?
> aren't burdened by the "right way" of doing things.
This is just another way of saying "have no clue what they are doing". There's a reason devs do thing the "right way".
Example: the other day someone was promoting their saas. They proudly advertised that they knew nothing about technology, and that AI created everything.
Yet their saas had a detailed privacy policy describing how your data was used. Of course the problem is, they have no way of knowing that their privacy policy is at all accurate. After all they don’t even know how to read their product’s code.
This undoubtedly exposes them to legal issues. I can imagine software being more tightly regulated as this spirals out of control.
We’ll hit a point soon where there’s so much dangerous and untrustworthy AI slop software on the market, that people will actively seek out and pay a premium for software created by professionals at reputable companies.
people are trying to dance around admitting that the fundamental premise of this entire approach is flawed and will always give inconsistent results.
"They laughed at Columbus, they laughed at Fulton, they laughed at the Wright brothers. But they also laughed at Bozo the Clown."
Considering how many developers still don't write tests, pair program, or do CI and CD (shipping multiple times a day) – all things Dave argues for – I don't think it is fair to dismiss him as the establishment or incumbent.
AI as a tool for software development is here and will continue to gain traction. Everyone recognises this.
But what is touted as "vibe coding" now is hype at best and misguided.
So I would instead argue that this is not the "innovator's dilemma" at all, and in fact AI is making headways everywhere, but instead this a classic hype cycle. Currently "vibe coding" might be peak hype, it will bring disillusionment when reality catches up, and so on as we go down the cycle.
Many "new ways" of doing something die before becoming the norm. Using the examples where it prevailed without looking at all the times it failed is just bad rationale.
"vibe coding" (what a horrid jargon) may be the new digital camera. It also may be the new metaverse (just to use a recent example still fresh in people's minds).
Contrary to digital camera and iphone, "vibe coding" is muddled by an army of people deeply invested in Gen AI adoption (either directly or indirectly) that want it to succeed no matter if it makes sense or not.
I see, so the solution is to adopt something that is worse because it is popular because people will build things 'because they can'.
Maybe we can shift towards vibe-designed finance, science, etc using LLMs 'because we can'.
The scenario is perfect, a use case that is not currently supported but may well make sense. It’s basically sketching out an idea to let business evaluate its market viability, and to gather further end-user input.
Will the code reach production? It just might, but it at least needs review and refactoring by a developer seasoned in the framework. They might even want to rebuild it, and then they have the yard stick which to measure their output. And if they need a specification, it can be generated from the code in which ever specification format required by their processes.
The key here is that I’ve been able to iterate on the POC many times in a short time. The idea sketch has been refined, necessary details added, while others removed. Functionality swapped in and out while testing different approaches.
Right now vibe coding in this way requires substantial experience in software development to frame the problems and solutions to the AI. Without my understanding of the domain (both the software domain and the actual domain) vibe coding the POC would not have succeed.
My greatest concern is that it looks and works too good and thus will be kept as is even in production. As the old adage says: There are no temporary solutions, just more or less permanent solutions. A temporary solution that works is a permanent solution.
The real divide going forward will be between vibe coding with experience across domains vs vibe coding without IMHO.
I've been trying to improve my productivity recently, so I vibe coded some scripts that help me record and analyse my time. I understand the code at a high level, well, maybe 80% of it anyway.
This debate doesn't mean anything to me, I'm just going to keep vibe coding.
It's fun having a backend, writing a few lines and after some minutes of waiting you have a fully working and decent looking frontend website available.
3 days ago i started modifying a kanban editor that was available for vscode. i wanted to have it compatible with an obsidian markdown kanban format i was using. but obsidian is to slow for me.
after 3 days it's not only working, but as far as i can tell it's a way better kanban editor then most of the ones i tried on vscode's extensions. of course i have specific needs (no dates, deadlines, priority), but a nicely tightly layouted interface with fast editing possibilities.
i would not have gotten this far in 2 weeks without claude code. i know i havent reviewed most of the code, except saving and loading. so it will likely look bad.
edit: in case you are interested: https://github.com/ludos1978/markdown-kanban-obsidian
So if I have 20 years of experience writing working code, “vibing it” is frustrating because I now need to master a “prompting language” which is not how I speak at all, it’s nondeterministic and fuzzy, and I need to threaten and beg simultaneously, and tell it to not hallucinate, or else I kill its mother.
Another “but” is that my today’s prompting is not at all guaranteed to produce the same results tomorrow! Companies keep tweaking their models and system prompts all the time. Today I’m the “A” in their A/B testing, and tomorrow I’m a “B”. And models that can be run locally are not useful enough yet. All in all, it resembles playing a slot machine where it gets you small winnings once in a while to keep you going.
If my subscription runs out, or the LLM provider goes under, I’m afraid all my outsourced knowledge goes with it. It’s too easy to get lazy if the machine gives you the abovementioned small winnings, just as it is easy to forget that even ubiquitous things like bread in stores and indoor plumbing are a privilege.
Also, people seem to be missing that "AI Assisted" coding and "Vibe Coding" are not the same thing.
Personally I think the issue with vibe coding is two fold:
1. It is not good at solving problems that are uncommon.
2. It is not deterministic.
Yes, AI can do quality control and testing now. But anyone who has done TDD can tell you that just the mere presence of tests does not itself mean the code is effective or solving the right problem.
Is it getting better? Yes. Do I trust any vibe coded apps built by people who don't know actual code and are treating it like a black box? Absolutely not.
And I say that as someone who has tried pretty much every IDE out there and uses AI assisted coding (on "agent" mode) heavily every single day.
12 more comments available on Hacker News