Earlier quoted context omitted.
Not even that, I'm not a civil engineer, but it looks pretty hard to add a ton of concrete without really helping a skyscraper, but I could add a few thousand lines of code without improving a system one bit, and even more lines to make the system slower, more complex, and still not add any functionality. LoC is about as good a measure of a system quality as weight is for an aircraft project.
You might acknowledge this analogy is popularly ascribed originally to Bill Gates. “Measuring programming progress by lines of code is like measuring aircraft building progress by weight.” ― Bill Gates
-2000 Lines of Code (2007)
221–222 of 222 posts
Re: -2000 Lines of Code (2007)
#222Earlier quoted context omitted.
The trick is to align the metrics with company goals. It's not easy, but not impossible either. For example, if quality is your goal, then the metric you give your devs is "number and severity of bug reports coming in from customers". If unsatisfied feature requests are part of that number, then the devs have to strike a balance between churning out features and preventing bugs (and fixing discovered ones). Obviously…
Ye and you end up with blame games and hot potatoes being passed around. Bug count metrics incentives "don't touch anything" and coding with feuture flags and globals to limit the scope of change and circumvent the architecture. Like, just don't do metrics and have the management actually review the work of their subordinates if that is important to follow up on. Actual management can't be compressed to a acting on s…