All software developers know that measuring a developer’s productivity by counting lines of code written is not an effective way to measure their output. The correlation between the technical difficulty of a problem and the number of lines of code is not always 1:1. Which means that one developer can write 10 lines in a day and be very accomplished, while another could copy/paste a solution of 1000+ lines in a day which was trivial.
On the factory floor managers always should be measuring opposing indicators. If you’re measuring the volume of output – you also need to measure the quality of output in order to prevent creating an unbounded method for taking advantage.
For example. If a manager of Intel processor factory production line focused solely on the number of chips produced each day, and cancelled all quality control checks then production output would likely skyrocket. In short order, however, the defects would be found by customers, the business would suffer. On the other extreme, if the manager focused solely on quality and checked every aspect of each chip produced then costs would skyrocket and output would crash.
The problem with measuring a software developer by the number of lines of code they produce is that there isn’t an opposing measurement of the quality/difficulty of those lines. Gauging the quality or difficulty of the produced code would likely require peer review, and for that peer to grade the code. Nobody wants to be the ass that gives their co-workers D- grades on their code so it becomes difficult to get honest scores.
In my opinion, counting anything is better than counting nothing. If Bill suddenly goes from committing 100+ lines of code per day down to 10 lines per day it may indicate something that a manager should investigate. If you weren’t measuring output then it would be impossible to know about or fix anything that Bill was having trouble.
Authors measure themselves by pages written per day. Writing 10 pages of crap is better than ending the day without having written anything. At least once things are on paper they can be communicated and others can help edit things to find the gems inside.