> even if the actual code Works - which I think is the number one most important thing about code

The ability for the team reason about the code, why it works (or not) is at least as important as whether it "works". Writing code that "works" for some short period of time is often trivial. There are situations when that's necessary or acceptable (solo project, proof of concept, short runway startup, whatever). But it's a debt decision that must not be taken lightly.

> Working only with Good code is a luxury decision

It's the cheapest decision long term. And that's even before measuring staff retention and other cost driving factors.