Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's worse than that. There is a standard way of assesing programmers productivity and is the worst it could be: kLOC's.


> Measuring programming progress by lines of code is like measuring aircraft building progress by weight.

--Bill Gates.

My favourite consequence of measuring productivity by the line is to ask how much I owe my employer when I spend a day eliminating redundancy and thus contribute negative lines of code.


Basically every programmer I've worked with agrees that kLOC is a terrible way of assessing productivity. I think it's only "standard" in the stupid section of the industry (which, alas, is much bigger than it should be).


Actually, I've always seen kLOC as a divisor: defects/kLOC, branches/kLOC, etc. Even metrics like functions/kLOC are useful, if you believe in small functions.


We use stats like this to help us gauge the project as a whole, but its considerly likely to be useless for measuring individuals productivity etc.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: