Values
Outcomes before artifacts
Ask why you care. Judge the system by what it does, and its code by what that costs.
“Quality” means little until you break it into named qualities and tie each one to an outcome. Those outcomes include behavior, maintainability, ease of change, operability, user success and business success. Untidy code is fine when it meets the qualities you named, and fast output that doesn’t create value isn’t.
The trap
You judge by the artifacts you’re used to judging, like tidy code and coverage numbers.
When artifacts are right
- A property of the code predicts an outcome. Complex code costs an agent more to change, just as it costs a person.
- A metric hides gaps. Replace it with a better one, as mutation testing shows what code coverage can hide.
Where it shows in the grid
“Define and enforce the qualities you care about, or don’t expect them,” and the Consequence row of the principles grid.