3 ms·
Having seen many other instances where chasing numbers has lead to a worse outcome, I think "metrics driven development" is an abomination that must be abolishe
by userbinator 6y ago
Having seen many other instances where chasing numbers has lead to a worse outcome, I think "metrics driven development" is an abomination that must be abolished. Unfortunately, management seems to really like the idea of turning everything into a number and increasing it at all costs --- I have fought against such things, and when I pointed out all the negatives associated with it, they would often agree; but then dismiss the thought completely with a response that essentially means "but it makes the numbers look better."
As the saying goes: "Not everything that counts can be counted, and not everything that can be counted, counts."
- theomh 6y agoI think what you are describing is a case of Goodhart's Law: "When a measure becomes a target, it ceases to be a good measure." https://en.wikipedia.org/wiki/Goodhart%27s_law https://en.wikipedia.org/wiki/Goodhart%27s_law On the other hand, a true accessibility score (for example, one awarded by a human or a robust grading process) could reliably quantify accessiblity. Goodhart wouldn't apply in that case.
- l0b0 6y agoYeah, as a TDD advocate this is the most common objection leveraged against that methodology: code with 100% test coverage can still be complete crap. And I agree. If you add test coverage only to increase that metric the result is likely going to be crap. If instead good coverage is a side effect of a healthy development cycle it's likely the code is going to be excellent. Basically, the metric should never be the goal, but discovering after the fact that your code does well on a metric is a good sign.