Earlier quoted context omitted.
While not everyone on HN is a developer, it does tend to skew that way so I don't feel guilty pointing out how frustrating it is to measure the output of a top programmer. Often, a mature codebase shrinks as code quality improves. This drives the efficiency wonks absolutely bonkers.
>This drives the efficiency wonks absolutely bonkers. what do you mean by that?
When a codebase shrinks AND increases in quality, you've now demonstrated that the most obvious way to quantify the utility of a resource - units of productive output - is not useful. So now people who are used to tallying widgets and graphs that are "good" if they move up and to the right, now have to understand things like refactoring, technical debt and design patterns.