🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.os.msdos.programmer
Article #1332

Re: counting keystrokes

#1332
From: Dwight Wilson
Date: Mon, 07 Sep 1992 16:42
46 lines
2615 bytes
In article <rvs.40@parst1.UUCP> rvs@parst1.UUCP (Roelof van Suilichem) writes:
>In article <1992Aug25.141521.17854@ucunix.san.uc.edu> edavis@ucunix.san.uc.edu (Ellen Davis) writes:
>
>
>>       I am posting this for my husband.  He needs to be
>>able to count how many keystokes were pressed when using
>>WordPerfect.  (His boss wants to see how much work the 
>>secretaries are doing.)  Any suggestions (and source) are
>>very much welcomed.  Thanks in advance.

First to answer this question.  Get the WordPerfect Developer's Kit.
WordPerfect has a hook that allows you to examine keystrokes before
the program gets them.  (They illustrate this with a small program
to expand abbreviations).  I'd post the info, but I don't have it
handy.

>
>
>(sing-song voice): .....Big Brother is WATCHING you...!!
>Your husband's boss is sick.  You check how much work people are doing
>by helping them set work goals, and checking if these goals get achieved.

An understandable, but perhaps misinformed knee-jerk reaction.  

There are jobs where a count of keystrokes (or keystrokes/hour) is
a valid measure of performance, for example transcriptionists.  Setting
goals is all very well, but the keystroke data may be essential in
determining whether those goals have been met.  In addition to measuring 
the quality of the workers, this could also be used for evaluating the 
benefit of add-on packages, different macro sets, etc.  This sort of 
tracking IS done by transcription services.  Whether or not this 
appropriate for Ellen's friend's boss depends on what tasks the 
secrateries are performing.

>
>Politics aside, I don't think this scheme will work anyway, because a
>lazy person will sit with a thumb/book on the spacebar for half an hour
>while doing something else.  It will also look as if the inaccurate typing
>person does more work (more backspaces).
>

Obviously you also need to collect data on the size of the output
files produced.  In addition to the raw data, the ratio between
output produced/keystrokes would probably be of interest.

-Dwight
Technical Details
Message-ID: <1992Sep7.164223.15136@blaze.cs.jhu.edu>
Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!darwin.sura.net!blaze.cs.jhu.edu!rhombus!wilson
References: <1992Aug25.141521.17854@ucunix.san.uc.edu> <rvs.40@parst1.UUCP>

Show Full Headers
Complete Article Headers
Newsgroups: comp.os.msdos.programmer
Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!darwin.sura.net!blaze.cs.jhu.edu!rhombus!wilson
From: wilson@rhombus.cs.jhu.edu (Dwight Wilson)
Subject: Re: counting keystrokes
Message-ID: <1992Sep7.164223.15136@blaze.cs.jhu.edu>
Sender: news@blaze.cs.jhu.edu (Usenet news system)
Organization: The Johns Hopkins University CS Department
References: <1992Aug25.141521.17854@ucunix.san.uc.edu> <rvs.40@parst1.UUCP>
Date: Mon, 7 Sep 1992 16:42:23 GMT
Lines: 47