Re: that Strong word

[Archie Ziviello <aziviello -at- NESL -dot- COM>]

How do you slip such abusive headings into a reference guide?

"DO YOU KNOW HOW LONG IT TOOK ME TO TEST/CONFIRM AND REFERENCE OUT THIS LITTLE BIT OF INFO LOSER?  MAYBE YOU SHOULDN'T COMPLAIN ABOUT THE MANUAL ANYMORE"

-----Original Message-----
From: Aoidìn Scully [mailto:ascully -at- FLEXICOM -dot- COM]
Sent: Wednesday, August 11, 1999 10:20 AM
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Subject: Re: that Strong word

I'm doing troubleshooting-y instructions at the moment for a piece of
software that is so simple to use, I feel like using a similar
construction; "Just read what's on the screen and do what it says, you
f***ing idiots!! Who gave you a job anyway?"

-----Original Message-----
From: Jim Cort [mailto:jcort -at- TOTALTEL -dot- COM]
Sent: Wednesday, August 11, 1999 2:47 PM
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Subject: Re: that Strong word

I gotta tell you,, "F---ing with the server." Sounds pretty good to me.
Sounds like that's what the guy's going to be doing.

Years ago when I was a programmer I had a brainstorm concerning error
messages.  I decided if the user put in the wrong code, an error message
should come up reading "Incorrect Code".  If the user made the same
mistake
again, a different message would come up: "Incorrect code.  Can't you
f---ing read?"

For some reason my boss wouldn't go for it.

Jim Cort
Technical Writer
TotalTel
Jcort -at- total -dot- com <mailto:Jcort -at- total -dot- com>

========================================================================
===

===========================================================================

 From ??? -at- ??? Sun Jan 00 00:00:00 0000