|
I hadn't given it much thought in the larger sense--thought of it as a technical problem. Seems like there are ways other than logging what people do at their workstations to measure productivity or whatever you want to call it. Setting clearly defined goals, examining the quality of the person's work, and making sure the person understands (or at least claims to understand) the requirements could provide a foundation for either improvement or whatever. My brother is a lawyer (not me) who specializes in employment law and works for a large company. Part of his job (not the most pleasant) is advising supervisors how to fire people. From what I can tell, the secret is documenting instances when standards aren't met and making sure that the employee has had opportunities to understand that there is a problem and has received clearly defined chances to improve the situation. I don't envy you. > -----Original Message----- > From: bmorris@ca.ibm.com [mailto:bmorris@ca.ibm.com] > Sent: Tuesday, December 07, 1999 3:52 PM > To: MIDRANGE-L@midrange.com > Subject: Re: Auditing Programmers > > > > > > >Arlene_M_Soderlund#s#NFCNA.COM@nfcna.com on 12/07/99 12:14:49 PM > > > >What AS/400 Journals, programs or methods, if any, will > audit programmer > jobs? > >Augh, I know it is the one that ruins it for the others and > I think I > have one > >of those here. I think the person has been away from the > desk for at > least an > >hour! > > Why does this matter? Does a programmer have to be typing > constantly to be > working? Maybe they were thinking. Maybe today just isn't > their day and > they are taking a walk to clear their head rather than write an hour's > worth > of buggy code that will take between hours and never to debug. > > Assuming there is a problem with this person, you shouldn't > have to catch > them > "napping" to prove that they aren't doing their job. > > The implication in "ruins it for the others" alarms me. > > Barbara Morris > > > +--- > | 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 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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.