If you meet requirements, do lines of code then become a viable measure of productivity?
edge.org
edge.org
The SoC programmers on the other hand generally have all the big blocking operations taken care of ahead of time by the SoC managers and mentors, allowing them to focus just on the coding.
I think a really cool metric would be who has the fewest lines of code per completed user story.
How long is the summer anyway, three months? So 20000 lines could be about 200 lines per day?
In fact, I think the lesser amount of code for the same size project is more productive. I'd prefer the programmer who can meet the project goals in 4,000 lines of code over the one who does it in 20,000 lines. Given those two numbers, I can't help but feel that the 20,000 lines is spaghetti code. (I realize this in my own prejudice and it may not be the case.)
As Antoine de Saint Exupery says: "Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away."
Going for perfection, in most cases, is probably not the most productive use of time. But I think this quote is still generally true for programming.