Link Details

Our ESP isn't working very well. Login and vote now.
Link 75326 thumbnail
User 225256 avatar

By mswatcher
via forums.construx.com
Published: Apr 13 2008 / 07:03

My last couple of posts on productivity variations among programmers and the Chief Programmer Team model gave rise to some discussion about hazards of measusring software productivity at the individual programmer level. Software engineering studies normally measure productivity in terms of time to complete a specific task, or sometimes in terms of lines of code per effort-hour, staff-month, or some other measure of effort. Regardless of how you choose to measure productivity, there will be issues.
  • 9
  • 1
  • 1574
  • 662

Comments

Add your comment
User 204329 avatar

ddelponte replied ago:

0 votes Vote down Vote up Reply

The lines of code approach is absolutely asinine. God forbid a programmer refactor and reduce the lines of code. Or on the flip-side, to look more productive, just generate lines and lines of crap. It's a fine measurement to use to get an idea of the overall size of your code base, but please do not link it to individual programmer productivity.

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Voters For This Link (9)



Voters Against This Link (1)