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.
Mark's comment sent me for my copy of "Handbook of Technical Writing"
3rd Edition (Brusaw/Alred/Olin), which defines Technical Writing Style
as:
Technical writing style is standard exposition in which the tone is
objective, with the author's voice taking a back seat to the subject
matter . . . the language is utilitarian emphasizing exactness rather
than elegance for its own sake. Thus the writing is usually not adorned
with figurative language, except when a figure of speech would
facilitate understanding . . . Good technical writing avoids overusing
the passive voice. Its vocabulary is appropriately technical, although
the general word is preferable to the technical word. Gobbledygook and
jargon are poor substitutes for clear and direct writing. Do not use a
big or technical term merely because you know it --make sure that your
readers also understand it. . . .Technical writing is direct and often
is aimed at readers who are not experts in the subject . . .
I agree that this is a description of technical writing style and,
though holes can be poked into the tightest yarn of logic, it seems
based in a logic to which I can easily adhere.
Paul
Mark Baker said "Technical writing is a job title, not a writing
style."
