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:Katherin King <kking -at- BROOKTROUT -dot- COM> Date:Fri, 8 May 1998 10:14:57 -0400
Mark Baker said, "A functional spec tells you how to build a product."
This isn't entirely true. Our software functional specs provide
excruciating detail about what the software does and how it does it, not
necessarily how it's coded/built. And yes, a lot of how I write the
users manual is to take that information and turn "what the software
does and how it does it" into task-oriented steps. Our product is a SDK
and runtime engine, used by developers to create telephony applications.
Kathy Stanzler
Technical Writer
Brooktrout Technology Inc.
Southborough, MA
(508) 229-7777 ext. 182
kking -at- brooktrout -dot- com
