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.
> For me, what makes a good technical writer is the ability to distill
> the essence of what the engineers/developers/SME's tell me into
> something that the product users can comprehend and use.
Characteristics I would add to those include
curiosity - What happens if I do *THIS*?
(note, this applies more to manuals for software
than manuals for the handling of high explosives)
self-confidence - The ability to not feel stupid asking
questions that engineers consider dumb.
strength - Writers work long hours when they receive specs
late but still have to produce the manual on
imagination - Even though I know this software package inside out,
I have to imagine I'm a new user who doesn't know
anything about it.
diplomacy - We all know why this is needed!