HN

Comments (67)

• Menu

  Thorrez
  For 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-toolDisclosure: I work at Google, but not on anything related to this.
• Menu

  doug_durham
  “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.
• Menu

  simonw
  Why 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.
• Menu

  monksy
  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 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.
• gobdovan
  Coding with AI is kind of like obesity in modernity: having tons of resources is the goal, but once you get there, you end up in a system you're not really adapted to.Personally, I don't care that much about org incentives (even though they obviously matter for what OP posted) but more about what it does to my thinking. For me, actually writing code is what slows my brain down, helps me understand the problem, and helps me generate new ideas. As soon as I hand off implementation to an LLM (even if I first write a spec or model it in TLA+) my understanding drops off pretty quickly.
• Menu

  keeda
  A lot of bad software today is attributed to "vibecoding" even though these trends have been existing since before LLMs. Like, people have been complaining about Windows for decades before AI came on the scene, except these days the same issues are attributed to vibecoding.I feel people are just lumping two things they don't like together because they are plausibly related, but without any real proven causality between them. Is this site any different?
• Menu

  crazygringo
  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.
• OsrsNeedsf2P
  I would be interested in a comparison of SLOs, "Before and after" adopting AI
• Menu

  porcoda
  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.
• nubinetwork
  What about all the o365 outages and windows bugs caused by ai written code?
• shermantanktop
  So 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.
• Menu

  bluegatty
  '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.
• aimadetools
  Thats already a big list
• ares623
  I 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.
• Menu

  dzonga
  why is this flagged ?
• cratermoon
  I cannot read dark grey text on a black background
• 22hsG
  Simon Shillison appears, comments that hurt his income stream are flagged.
• blinkbat
  Lol @ this being flagged
• Menu

  Dig1t
  I 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.
• rvz
  This is the web3isgoinggreat equivalent for crypto, but for vibe coding with AI.
• cjrd
  now do one for human-coded incidents.
• 5129-dqw
  [flagged]
• Menu

  tonymet
  AI might have been an opportunity to take engineer hubris down a knotch. Perhaps to reassess the excesses (bad performance, bad UX, poor reliability, costly development & operations, etc) . Instead of reflection, we decided to shame AI as vibe coding .How much abysmal code and products have we all shipped? Exploitative, clumsy , dangerous, vulnerable? What was our excuse?I find the entire anti-vibe coding movement to be terribly tacky and judgmental.We have an incredible tool that could 10-100x productivity. We should be using it to fix all of the terrible software we’ve made over the past 20 years. Instead there are 2-3 camps. People building stuff, people hyping AI and people shaming the first 2.Sad, really.
• Menu

  wa5ina
  A curated directory of documented incidents where AI-generated and vibe-coded software failed in production.