[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.

[bigstrat2003]

> 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.

[simonw]

> Only among people who don't value the quality of their output.

I value the quality of my output and I make extensive use of AI tools.

That's why the original definition of "vibe coding" is useful: creating code with AI tools without reviewing or caring about the quality of that code.

It's also possible to use AI tools as part of a responsible engineering process that is intended to produce production quality software.

[eloisant]

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 saying they can't be useful means you haven't taken the time to look at the state of them recently.

[onion2k]

Isn't it odd that you wrote your comment with AI then!?

Ha, gotcha, AI slop poster!

I know you didn't, but this is where we'll end up if people just write off everything as 'bad because AI' instead of critically assessing the quality of something on its own merit rather than the (very ironic) 'vibe' that it was generated rather than written.