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: What does a tech writer do? From:Susan Fowler <sfowler -at- EJV -dot- COM> Date:Thu, 8 Sep 1994 15:59:17 EDT
What really bothers me is that many of my friends and relations think that it's
their fault when they don't understand something or can't get something to
work. I spend most of my time explaining that it's _not their fault_ if the
product is badly designed or the manual is badly done or translated.
The OTHER thing that really bothers me is that folks in the tech writing field
have, over the past 10 years developed writing, illustrative, and design styles
that almost guarantee understandability. (Is that a word?) Much technical
writing is remarkably good. But we don't get credit for that, ever.
