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:That's Entertainment! From:Tony Rocco <tony_rocco -at- NAVIS -dot- COM> Date:Thu, 27 Jun 1996 10:16:54 U
Forgive me for being a fuddy duddy, but I don't believe that good
documentation need be "entertaining." I know that the "XXX for Dummies" books
have made a fortune being entertaining, but they are addressed to a
non-technical audience that needs humor to maintain interest and allay
technophobic anxieties. This is a valid approach *for that type of audience*,
but for most computer-related audiences it would be inappropriate.
I think good technical writing should be *interesting* and have some sort of
stylistic appeal, visually and editorially. But I stop short of it being
"entertaining," with jokes, whiz-bang graphics, loads of funny-looking icons,
etc. These devices often interfere with clarity of expression and make it
harder for the reader to find needed information as quickly and easily as
possible.They also wear thin after the tenth time you have seen them.
If the rap against Information Mapping is that it produces bland,
uninteresting documentation, it is well-deserved. If the complaint is that it
results in documentation that is not entertaining, like DOS for Dummies, it
is not so merited.
- Tony G. Rocco
TECHWR-L List Information
To send a message about technical communication to 2500+ list readers,
E-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send administrative commands
ALL other questions or problems concerning the list
should go to the listowner, Eric Ray, at ejray -at- ionet -dot- net -dot-