Lines of Code Metric
Comments debate the flaws of using lines of code (LOC) as a measure of programming productivity, quality, or progress, often citing Bill Gates' quote likening it to measuring aircraft by weight.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Lines of code isn't a good measuring stick.
Lines of code is a pretty bad metric.
Lines of code is a bad measure even if it's not a target.
The 14.9k LOC guy is correcto. Let's burn in a stick the heretic 0.1k LOC coder
Measured by lines of code written, no doubt...
"Lines of code are not produced but spent" (can't remember the author)
why does (current) number of lines of code matter
Lines of code is a poor way to measure contribution.
Absolutely.I think some of these people need to be reminded of the Bill Gates' quote about lines of code:“Measuring programming progress by lines of code is like measuring aircraft building progress by weight.”
Lines of code is not an absolute metric for quality but it is a good rule of thumb (unless raw speed us the characteristic you are optimizing for.) Less code means the program or routine will be easier to read and understand and have fewer places for bugs to hide. Of course, this means lines of code in the syntax and standard libraries of the language: a program that calls a third-party library should be viewed as one that counts the lines in this library as well.