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:Re: Style Manuals From:Philomena Hoopes <PHILA -at- MAIL -dot- VIPS -dot- COM> Date:Wed, 3 Feb 1999 10:46:55 -0500
I'm seeing a philosophical difference between technical writing as creative
endeavor and technical writing as tool-building. My perspective is that the
writing should be as unobtrusive as possible to present new information
without the distraction of unfamilar packaging.
If I'm documenting programs in a Windows environment, and the lingua franca
happens to be developed by Microsoft, well, them's the breaks. If I were
documenting programs in a VAX/VMS or UNIX environment, I'd make it my
business to learn and use the associated terminology. When I want to use
language with creative panache, I can write poetry or fiction, or freelance
with magazines or ad agencies. My purpose in writing manuals is to be
understood, not to dazzle the reader with my artistic originality.
To use an analogy: imagine what would happen if each car manufacturer used
entirely different terms for electrical and mechanical components and
Phila -at- vips -dot- com <mailto:Phila -at- vips -dot- com>
VIPS Healthcare Information Solutions, Inc.
(410) 832-8330 ext 845