4 ms·
you may need to look at bugs/ksloc as more of an enterprise measure than one for an single project. when it gets down to it, this is the measure that will tell
by bdavis__ 7y ago
you may need to look at bugs/ksloc as more of an enterprise measure than one for an single project.
when it gets down to it, this is the measure that will tell you if your organization is 'improving'; end of the line reducing your defect rate is one of the most valuable things to accomplish.
- kqr 7y agoAssuming it's more noise than signal, increases or decreases to that measure don't tell me anything about actual improvement. I'm all for reducing the defect rate, I'm just not convinced optimising bugs/kloc is meaningful.
- StillBored 7y agoWell anything done directly to influence bugs/kloc is bound to throw the whole thing off. I think the parent here was mostly interested in discovery rate, which also can be influenced by hiring/firing test and QA, or for that matter gaining/losing customers that use the product. And everything being mostly equal, it could be a reflection of code maturity more than anything. The more mature product may have a higher bug/loc ratio only because more of the bugs have been found. Which is why I mention there are metrics, but they all seem to have major problems.