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.
Re: Culture, or What it means to be a Technical Writer
Subject:Re: Culture, or What it means to be a Technical Writer From:"Hutchings, Christa" <cwhutchings -at- HOMEWIRELESS -dot- COM> Date:Fri, 8 May 1998 13:22:59 -0400
Janice Gelb wrote:
For example, at a previous company we had a writer
who was very good at anticipating possible ways users might try
to use the product and get themselves into trouble. He would ask
the developer "What happens if the user does x?"
Wow, I'd like to hire that writer!
The developer would reply, "But, but.. that's not the way
they're supposed to do it!"
And how often we run into developers like that!
In no way is a scenario like this translation -- it's,
as someone else put it nicely, "getting into the user's head"
and providing them with information accordingly.
Amen!
Chris Welch-Hutchings
Sr. Technical Writer
Home Wireless Networks, Inc.
Norcross GA (USA)
cwhutchings -at- homewireless -dot- com
