It's not just codebase, it applies to product, design and even human interactions.
It's hard to describe how important I think this principle is for a project, company or even life.
It's hard to describe how important I think this principle is for a project, company or even life.
In a corporate environment, if you can measure something with a number, then you can set a target and pass/fail criteria and so on. Developers' personal opinions of some code base's quality are harder to build corporate processes around.
There's things like integration tests and static analysis. Of course again, not foolproof and don't solve all problems. But they help. Especially in a corporate environment where you need all the mechanisms you can get to prevent skimping on quality.