Re: Mandatory Job Log

You were "starting to get really annoyed"?

I've threatened to break users' fingers for less.






"Barry L. Kline" <blkline@xxxxxxxxxxxxx> wrote in message news:mailman.3271.1326147068.2619.midrange-l@xxxxxxxxxxxx...

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/09/2012 02:18 PM, paul therrien wrote:

For really important stuff you make the user actually key in the
word 'YES' or 'DELETE' --- don't take ENTER for an answer! :-)

Years ago I had an inventory clerk who repeatedly accidentally ran
"year-end", which resulted in a significant amount of work to fix.
(This was on a System/34). My solution was to add a prompt asking him
if he actually wanted to run it, requiring "YES" as a response. He
unceremoniously keyed YES and ran the wrong thing anyway. So I added
another iteration of it. He screwed it up again. I added another...
and again another failure. After the third time I generated a
random 32-digit number and required him to key that in as the final
"launch code." Problem solved.

Okay, perhaps it was overkill but I was starting to get really annoyed.

Regards,

Barry