It’s never about the tool, but about the responsibility. In humans are those that take responsibility for the tool they use, be it vim or opencode.

Most software teams I’ve seen were pushing things they don’t understand well before AI

Vibe coding is just a really big hammer, what you do with it and what you do with results is still up to humans. Even if this was result of it, fuckup is ultimately fully in hands of somebody responsible (for product, website, clients etc).

If not, company is not viable and will crash badly soon. Market forces and all that.

For the vast majority of these issues, certainly including those mentioned here, simply testing before going live would make them beyond clear. So it's simply a bad developer likely working under bad management and, shockingly enough, producing a bad outcome.

LLMs will be an interesting test of the current broken systems at most large companies. You can literally fire your entire engineering team and replace them with your "really smart cousin" and Claude. And that's going to be mighty tempting when the MBA mantra seems to be that cost reductions this quarter are infinitely more important than any potential costs in the future. But of course they're not.

So as I understand it, vibecoding means (meant?) that you don't look at the code it produces, you case only about the end results, e.g. website through a browser.

But in this case, they seem to have skipped that as well.

Vibe-coding is a skill (like tying shoelaces), not a tool. And there's always room for improvement.

I'm sure it's both different groups of morons, but the constant shifting back and forth between "if you're reading code in 2026 you're wasting time" and "you wouldn't blame a hammer if you hit your thumb" is absolutely hilarious. LLMs are either a simple tool or a hyper-intelligent system depending on which characterization is anticipated to sell the most snake oil in any given instance.

At the very least, if these are indeed different groups of morons, one group is shutting up whenever the other is spewing their flavor of bullshit.

If I had a dollar for every RoR coder who didn't understand the internals of the interpreter I would still not be richer than Musk because there are not that many coders.

No one at any company has ever understood every bit of the stack they ship; see all the bugs AI is finding in all the frameworks and libs we been shipping this whole time; oh yeah we sure knew what we were shipping.

git pull git@github.com:allofit/allthethings.git engineering patterns is what created this mess to begin with

And even if you don't carefully review each line of code (or if you do), it helps a lot if you understand the basic principles of what you're trying to build. In this case, the vibe coder clearly had no idea about account security standards.

Programmers don't just write code. They also understand why they're writing the code and what it's supposed to do.

My SOTA LLM spends disturbingly much time stopping me and telling me to shape up and do things right, especially on the security/legal/privacy side. Speaking from recent experience, it would NOT have anything CLOSE to this—I’d expect it to literally refuse to ship.

Whether that says more about me or about LLMs These Days, I’m not sure…

I don't think it does, I doubt SOTA models are going to sign off on this.

On the other hand, people incompetent enough to ship this couldn't have produced a working website if they had to handwrite the code, so in that sense LLMs are at fault.

The human who thought pressing publish on this wouldn’t have thought stopped to think about security even if it was handmade.

> Stats say what, 80% of programmers use AI to generate code? 90%?

I am extremely skeptical that those numbers are even close to accurate.

>So everything is vibe coded.

Given the sentiment that software is getting worse, buggier, and overall less stable, that isn't a comforting statement.