Re: Job Accounting

[boothm@xxxxxxxxxxxxxxxxx]

I'd agree keystrokes isn't the answer. 

But what does work well?  How do you tell how a programmer is doing 
on-site?  Why wouldn't the same measures work off-site? 




Please respond to MIDRANGE-L@midrange.com
Sent by:        owner-midrange-l@midrange.com
To:     MIDRANGE-L@midrange.com
cc: 

Subject:        Re: Job Accounting

Paul,

>Well, you get the picture.  It's very difficult to analyze exactly what a
>programmer does and what counts as 'productive' time.

And not only that, but a programmer is more productive when running
multiple sessions (or at least I am), with each session "active" in
the sense that they are not just sitting at a menu.  So they would
appear to have long think time waits, when in reality I could be busy
pounding the keyboard in another session.

I'd hate to be limited to one session just so someone could monitor
keystroke activity, especially since I vastly prefer to use a PC-based
editor instead of SEU.  That wouldn't show up in the statistics very
well either...


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