Re: Auditing Programmers

Why can't you look at their project / completion ratio. If you were to implement
some sort of change management system which also monitored an applications 
status
in the development and testing cycle then you could get a better idea of
productivity based at the project level.
I agree with you that monitoring system usage is to easy to fake. I worked at 
one
shop where the team leader would look at the time stamp on each record in a
source member to guage how much work was done, even I see the flaw in that 
logic.

But one thing is sure, you can't just look at things such as system usage as an
indicator of programmer productivity.

Chris Bipes wrote:

> Agreed.  I was one of them years ago.  My point is they are burning CPU
> cycles but not very productive from a production point of view.  They are
> learning which is good and hopefully gaining productivity.  Monitoring
> programmers is not easy, it is the managers hardest task.  The manager has
> to weigh the cost/benefit for a programmer.  Are they getting faster and
> more accurate?  Do they have good work habits?  Can they develop solutions
> to your business needs?  Do they fit the companies needs?  How can I monitor
> that on system?  Sorry don't waste your time auditing programmers system
> use.  It just does not measure their productivity.
>
> IMSO!
>
> Christopher K. Bipes     mailto:ChrisB@Cross-Check.com
> Sr. Programmer/Analyst   mailto:Chris_Bipes@Yahoo.com
> CrossCheck, Inc.         http://www.cross-check.com
> 6119 State Farm Drive    Phone: 707 586-0551 x 1102
> Rohnert Park CA  94928 Fax: 707 586-1884
>
> *Note to Recruiters
> Neither I, nor anyone that I know of, is interested in any new and/or
> exciting positions. Please do not contact me.
>
> -----Original Message-----
> From: Martin, Booth [mailto:BoothM@goddard.edu]
> Sent: Wednesday, December 08, 1999 8:28 AM
> To: 'MIDRANGE-L@midrange.com'
> Subject: RE: Auditing Programmers
>
> In my opinion they are.  Learning is reptitive, so they are learning, one
> step at a time.  Much quicker than the alternative.
>
> -----Original Message-----
> From: Chris Bipes [mailto:rpg@cross-check.com]
> Sent: Wednesday, December 08, 1999 11:02 AM
> To: boothm@goddard.edu
> Subject: RE: Auditing Programmers
>
> I have worked with very green programmers who use the compiler to find all
> their syntax errors.  They submit compiles of the same program 20-40 times a
> day fixing one error at a time.  Are they really working hard?  They sure
> burn the CPU cycles.
> +---
> | 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
> +---

--
L. S. Russell Programmer/Analyst
Datrek Professional Bags, Inc.
2413 Industrial Drive
Springfield, TN. 37172
mailto:leslier@datrek.com
http://www.datrek.com
--


+---
| 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
+---