3 ms·
Well yes, because that assumes that there is some magical amount of checks that must never be exceeded. Some checks are extremely valuable and should be added b
by run4yourlives 18y ago
Well yes, because that assumes that there is some magical amount of checks that must never be exceeded. Some checks are extremely valuable and should be added based on their merits alone.
- alextp 18y agoThat's the point I was trying to make. Something like "always commit and run the tests before going to production" makes a lot of sense, and should be mandated. Even something like "three signed copies of an authorization form" makes sense for some projects if, for example, the cost of damages (say, lost data, downtime or annoyed paying customers) is big enough. Measuring this, though, is the hard part. It's like trying to do the math behind "no silver bullet" and estimate communication costs (too many unknowns and conditional dependencies).
- eru 18y agoHow about just measuring how many bits it takes to describe the checks (perl code etc + informal text). Do not make any hard and fast rules - just monitor this metric.