To argue against this metric, I will use Reductio Ad Absurdum. Look at the finished software. Count the characters in the source code. All of the source code,

To argue against this metric, I will use Reductio Ad Absurdum. Look at the finished software. Count the characters in the source code. All of the source code, tests, comments, configuration files, whitespace, everything in the project's source. Divide by five. That's the number of words. An average professional typist can type at 50-70 wpm. we're professionals, so we'll take sixty. Divide the number of words by sixty to get the number of minutes. Perfect productivity for a professional-grade typist consists of spending that number of minutes typing out the finished software. Take the number of minutes actually logged by the entire team and divide by the perfect productivity number. If the team took twenty times as long, they have a productivity of 5%. If it took 1,000 times as long, they have a productivity of 0.1%. This is the same thing the author advocates, only I am suggesting that any activity except typing code that appears in the finished product is what the author calls a waste. Something stinks here.