“Measuring programming progress by lines of code is like measuring aircraft building progress by weight.”
It's appropriate on so many levels. Lines of code can be part of a measure of what has been accomplished, just like a heavy airplane is a great accomplishment so long as it flies. Yet we would never consider adding weight to be our goal.
It starts at zero and increases as the big pieces are added. It stops at a well defined number that is specified.
> “Measuring programming progress by lines of code is like measuring aircraft building progress by weight.”
Nice. And then we have Windows that needs dozens of gigabytes disk space and can do nothing useful at all, while debootstrapped Debian chroot can easily serve a dynamic website backed by a database and weigh two orders of magnitude less (minus the data, obviously).
The analogy is quite apt, but the context of the author's company makes the sentence hilarious.
[I]f we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent": the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger.