TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:invocations From:mpriestley -at- VNET -dot- IBM -dot- COM Date:Tue, 1 Feb 1994 16:25:39 EST
>***But***, Mike --
>If you've ever been faced with a classroom full of
>**novice** computer users who actually **believe** that...
>1) it **is** a magic box
>2) nothing they do can control the outcome because the box
> has a mind of its own
>you'd avoid the word "invoke" like the plague. If you think
>not, you've got another thin*g* coming!! %^)
A good point - the application I'm working on right now is for use by
experienced users only, so I didn't even think of that. However, when you
think about it, they might not be too far off base in their estimate at that.
Two hard and fast rules I've acquired over the years:
1) Ritually sacrificing the occasional white mouse to a computer increases its
mean time between failures by a factor of 10.
2) If you let the smoke out of a computer, it'll never run again. All
electric appliances run on smoke.
I think all this mumbo jumbo about "programming" and "logic" and
"specifications" are just pathetic little mantras we mumble in the vain hopes
of appeasing the vengeful computer gods. In reality, no one has any idea
exactly what will happen the next time you turn on your computer. It could
blow up, it could put a curse on you, it could turn into a dragon and eat you.
However, those fortunate few of us gifted with the power of prophecy have
gone into the soothtelling business, and call ourselves "Technical
Communicators" or "Information Developers" (our very titles are made of words
of power). You and me are in the business of writing spell books.
Kinda makes you go hmmm...
:-0 :-\ :-)
mpriestley -at- vnet -dot- ibm -dot- com
Disclaimer: not only do my views not represent those of IBM, but if they knew
what I just wrote they'd probably have me quietly taken away by nice people
in white suits and locked up for the next decade or so.