This is more like adding a third party dependency to your project without vetting it.

The problem is we have different terms that all mean doing something without real risk management or analysis in software. Both "cowboy coding" and "vibe coding" mean the same thing, if you remove the agent doing the production.

And since vibe coding is so recently coined, I think a lot of people take it to specifically mean "LLM" and not some generalized "any third-party agent".

Then, a vibe coded engine part sounds like it would need a generative AI producing the CAD file that is then printed. And it might have some bizarre topology like a Klein bottle or some fever dream.

>I think by vibe coding he means taking these things at face value instead of rigorously looking if they are up to the standard.

Yeah, exactly -- which is why it's a stupid phrase for what happened here.

Not every negligence is somehow equatable to an AI pitfall, it's just on parents' mind so it's the only metaphor that gets applied.

A poorly fit hammer in a world of nails.

I say this as an engineer/proprietor with years of additive manufacturing experience, it's insulting. A poorly chosen and wrongly used process conveys nothing about the underlying fundamentals of the process itself -- it conveys everything about the engineer and the business processes that birthed the problem.

Similarly if I came across a poorly vibe-coded project I wouldn't blame Anthropic/oAI directly -- I would blame the programmer who decided to release such garbage made with such powerful tools..

tl;dr : it's not vibe-coding itself that makes vibe-coding a poor fit to rocket science and brain surgery -- it's the braindead engineer that pushes the code to the THERAC-25 without reading.