The "Vibe Coding" Wall of Shame
crackr.dev
The "Vibe Coding" Wall of Shame
1–10 of 88 posts
Re: The "Vibe Coding" Wall of Shame
#2A curated directory of documented incidents where AI-generated and vibe-coded software failed in production.
Re: The "Vibe Coding" Wall of Shame
#3[flagged]
Re: The "Vibe Coding" Wall of Shame
#4I cannot read dark grey text on a black background
Re: The "Vibe Coding" Wall of Shame
#5Thought 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 scratching disconnect to the user, etc behaviors).
But I think this is a great thing to show that they're pushing to outsource coding to a bot and to shame them that their plan isn't working out so well as they're trying to force people to believe.
I think it may help if we start personalizing these trends with the people who are amplifying it. I.e. Jassyslop, Siemiatbot (Klarna CEO was bold to brag he dropped 80% of a role for AI) etc.
Re: The "Vibe Coding" Wall of Shame
#6“Vibe coded”? I doubt that there is the documentary evidence that the code in these systems was never touched by a human. At best this is a list of code where AI tools were used in development. To be honest if you just created a list of all outages in all companies and systems you’d probably have a better list since AI tools are ubiquitous.
Re: The "Vibe Coding" Wall of Shame
#7For CVE-2026-0755, that's a vulnerability in gemini-mcp-tool. gemini-mcp-tool's Github repo says "This is an unofficial, third-party tool and is not affiliated with, endorsed, or sponsored by Google." but this list shows the Google logo next to the vulnerability.
Also, it's not entirely obvious to me that the vulnerability was introduced by vibe coding.
https://github.com/jamubc/gemini-mcp-tool
Disclosure: I work at Google, but not on anything related to this.
Re: The "Vibe Coding" Wall of Shame
#8This is the web3isgoinggreat equivalent for crypto, but for vibe coding with AI.
Re: The "Vibe Coding" Wall of Shame
#9Thought 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.
Re: The "Vibe Coding" Wall of Shame
#10“Vibe coded”? I doubt that there is the documentary evidence that the code in these systems was never touched by a human. At best this is a list of code where AI tools were used in development. To be honest if you just created a list of all outages in all companies and systems you’d probably have a better list since AI tools are ubiquitous.
> 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.