In my experience over the last couple years, lists like this won’t move the needle at all. The AI zealots reject anything that calls into question the AI stuff, usually appealing to “just wait, better models/agents/guardrails imminent” and claiming that anecdotal productivity gains are worth the risk. The people concerned about AI already are concerned and just fall back to “I told you so”. Unfortunately the decision makers seem to still be following the zealots promising wondrous productivity, profit, and a future full of flying cars.
The "Vibe Coding" Wall of Shame
11–20 of 88 posts
Re: The "Vibe Coding" Wall of Shame
#12Why is the LiteLLM incident on there? The linked article for that one is a 404.
I didn't read any credible arguments suggesting that was caused by vibe coding. They had their PyPI publishing credentials stolen thanks to an attack against a CI tool they were using.
Plus the linked article for the Amazon outage is https://d3security.com/blog/amazon-lost-6-million-orders-vib... which appears to be some other vendor promoting their product without providing any details on what happened at Amazon.
Re: The "Vibe Coding" Wall of Shame
#13I kind of think that the "Human Coding" Wall of Shame would be quite a bit larger and contain examples that are every bit as egregious.
Re: The "Vibe Coding" Wall of Shame
#14[flagged]
Re: The "Vibe Coding" Wall of Shame
#15'vibe coding' is too loose a term. Everything will be generated by AI in the very near future, and it will range from 'fancy auto complete' to 'entirely autonomously generated' with many nuances and subtleties in between.
Re: The "Vibe Coding" Wall of Shame
#16So this is a list of incidents where random people on the internet speculated about rumors that AI was to blame. The companies typically deny it. Insiders who know the details are generally unable to comment due to how large companies manage PR.
So basically Reddit.
Re: The "Vibe Coding" Wall of Shame
#17Thought 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…
Honestly, we should shame companies for poor engineering whether humans are directly doing the work or handing it off to an LLM.
I agree with you. However, business individuals have decided that they're "a better judge" of our practices and they've used financial, legal, and coercion to get their way.
Re: The "Vibe Coding" Wall of Shame
#18Thought 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…
Honestly, we should shame companies for poor engineering whether humans are directly doing the work or handing it off to an LLM.
Everything is blameless, you can't do that to humans lol
Re: The "Vibe Coding" Wall of Shame
#19I love dunking on vibe coding as much as the next guy but is there actual evidence for most of the entries that such is the case? IMO that will make the point even stronger.
Re: The "Vibe Coding" Wall of Shame
#20What about all the o365 outages and windows bugs caused by ai written code?