I thought the same and it depends on which context you work. Below is an answer on slack from our CEO when I said talking about Claude code source leak : « Dirty, un-architected code is the new norm; it makes billions, who cares… »

He answered:

> Well, yeah, who cares?

> This is where we need to differentiate between what truly needs to be clean (critical APIs) and where some random guy coding a product in a week will wipe the floor with a team of engineers with a clean architecture and no product after three months.

> What's more, this "vibe coder" is on the right side of history… Who's to say AI won't be able to just rewrite the code cleanly while keeping the core idea within 6, 12, or 18 months?

> This is also the question that drives business... and in business, "good enough" has almost always trumped "perfect." Except when you're making an ultra-luxury product like a Ferrari or something. Which software almost never is (if ever).

So when head of companies don’t care about quality, they’ll push hard no matter what to have speed.