Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The "Vibe Coding" Wall of Shame

crackr.dev

Post reply on HN
Print view View original

81–88 of 88 posts

Re: The "Vibe Coding" Wall of Shame

#81

Post by Andrei_dev »

crazygringo wrote: post #37

Is this meaningful at all, without a control? How often does software fail in production with human-written code? How many times has a production failure been avoided because an LLM didn't make a typo or mistake that a human would have? This is pushing an agenda. It's not measuring anything meaningful.

Half this list is bad attribution. LiteLLM was a supply chain attack — stolen PyPI credentials, nothing to do with vibe coding. The Amazon outage number comes from a vendor blog pushing their own product. Nobody else reported it.

But the "where's your control group" take bugs me too. It's not that AI writes buggier code line for line. The gaps are just in different places. Devs who've shipped real apps add rate limiting, auth middleware, proper CORS — because they got burned before. AI skips all of it because nobody prompted for it.

I read through about 80 AI-generated repos a few weeks ago. Code looked decent. The missing stuff was always the same list — no auth on admin routes, API keys hardcoded in client JS, CORS wide open, debug endpoints still live in prod. Over and over.

Nothing there makes a wall of shame. Nothing's exploded yet. But it's the kind of stuff that does.

Re: The "Vibe Coding" Wall of Shame

#82

Post by ratrace »

eloisant wrote: post #33
bigstrat2003 wrote: post #10

Earlier quoted context omitted.

> AI tools are ubiquitous. Only among people who don't value the quality of their output. There are, fortunately, many who do value quality and are not using AI tools until they get to the point where they can usefully contribute.

Have you used a state of the art tool (e.g. Claude Code) in the past 6 months? If you only tried free tools, or only tried 1 year ago last, you really need to check again. AI tools can absolutely contribute usefully, I can't keep count of the times where an AI pointed to an edge case I didn't think about, then helped me write the fix and the test for the issue. I'm not vibe coding, as I'm reviewing the code, but sayi…

[dead]

Re: The "Vibe Coding" Wall of Shame

#83

Post by AbstractH24 »

monksy wrote: post #5

Thought experiment here: What about the bugs that humans have wrote. (I'm not excusing or justifying to say AI Coding is better). At one point we shamed companies for producing and being sloppy with their engineering practices. All of the sudden in the last 10 years, we accepted company's excuses of "of well we don't care and we're garbage." (A lot of Amazon tone death documentation/surprise bugs/google's head scratc…

enshitification is the issue, not vibe codeing

Re: The "Vibe Coding" Wall of Shame

#86

Post by chunpaiyang »

Andrei_dev wrote: post #81
crazygringo wrote: post #37

Is this meaningful at all, without a control? How often does software fail in production with human-written code? How many times has a production failure been avoided because an LLM didn't make a typo or mistake that a human would have? This is pushing an agenda. It's not measuring anything meaningful.

Half this list is bad attribution. LiteLLM was a supply chain attack — stolen PyPI credentials, nothing to do with vibe coding. The Amazon outage number comes from a vendor blog pushing their own product. Nobody else reported it. But the "where's your control group" take bugs me too. It's not that AI writes buggier code line for line. The gaps are just in different places. Devs who've shipped real apps add rate limit…

[flagged]
Post reply on HN