|
John, Define "work." Time signed on Time actually keying something Time reading something in a manual Time spent staring at the wall planning what to do Time spent writing code on a white board, with changes, corrections, and pseudo code Time reading the screen trying to figure out what the previous programmers did Time spent waiting for a compile to complete Time spent keying test data Time spent waiting for test run to complete Time.... Well, you get the picture. It's very difficult to analyze exactly what a programmer does and what counts as 'productive' time. --Paul E Musselman PaulMmn@ix.netcom.com >Hi everyone, > >We use contractor programmers on and off site. I am looking for some >software than can keep up with how much actual time a person works on the >system not just signed on. If anyone knows of this type of software I would >appreciate the info. > >Thanks; > >John Harrison >Nucor Steel - Arkansas >jharrison@nucorar.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.