Weedpacket wrote:The SLOC metricLegend has it there are development houses out there that pay their programmers by how many lines of code they produce. Me, I don't believe that such companies would be able to survive long enough to ship. But then, I tend to overestimate the intelligence of the average person.
And using such a simple and easily-gamed metric is a poor way to judge a programmers worth. Something that may take 10 condensed lines of solid code could easily be made into 100lines by the person payed per-line.
And "lots of lines" really is dependent on what's counted--code,comments,whitespace,etc--but still it's too vague to be used as a quality metric. If you assume the opposite of the pay-per-lines stance--more concise code is better--then you get crunched up code that is impossible to maintain. Somewhere in-between extra-bloaty and extra-tiny code is probably some happy zone where programmers might want to be.
For statistical purposes, I just ran an app I wrote the first 2/3 of 2006 (roughly) through K-LOC (I have doubts about it's accuracy and whitespace exclusion)....it came out to around 365,000 lines (again, I'm looking at that number with a skeptical eye)....and that's not including architecting/diagramming either. But again, that's not a good judge of either the quality of the code or the productivity of the programmer. Keep in mind in that same 8 months I also did 100% of the design/imagery/etc for the application--from scratch.....you can't measure that input by counting lines.
So if you want to count lines of code, go ahead, but remember it's a meaningless metric, because it it doesn't include quality, externalities, or even language into the mix (we all know you can take a berjillion lines of Java and crush it into one extremely cryptic line of Perl.).