• Subject: RE: programmer productivity.
  • From: "Denis Robitaille" <DRobitaille@xxxxxxxxxxxx>
  • Date: Fri, 10 Nov 2000 14:44:02 -0500

I'll jump in with some tought.

Measuring programers productivity is important but it is impossible to do 
perfectly. I do not think that LOC gives any indication on tne productivity of 
a programmer.

But i think that it is possible to partially evaluate the coding aspect of the 
job when we are talking new development. Here is what I saw:

Programs were categorized (batch, report, interactive, subfile ...) and each 
category was given a normal/average time to complete (20n hours, 50 ...). Those 
metrics are use to evaluate the project. Why not use the same metric to 
evaluate the programmer? Of course if the analysis was lousy, the end result 
may also be but this become the problem of evaluating the analyst (a much more 
subjective subject). 

Denis Robitaille
Directeur services techniques
Cascades Inc
819 363 5187
fax 819 363 5177

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].