Programmer productivity metrics

[chinglish]

I think you've missed the entire point of this thread. LOC is about the worst measure you could use to test whether something is well written. Chances are the better code in a project is concise and clear. The long winded code will hide potential issues that aren't obvious until out in the wild.

You missed my point which was first test the quality of code using open source tools available. These tools highlight useless/redundant code and programmers. If a programmer can't get his code to pass the quality checks then you don't need anymore metrics as the programmer is useless and you should get rid. If they can get through the quality checks then LOC remaining is one metric - on its own useless but a metric of quality code produced. The previous argument that a programmer can make their code long winded no longer exists as an automated code checker is included to highlight it. You can also when re-factoring use LOC removed - as a metric for how much more efficient the code is.