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: Telecomm writing vs. Software writing From:Wendy Lewis <wlewis -at- NCLOGIC -dot- COM> Date:Mon, 14 Jun 1999 10:01:28 -0400
I too write software for phone switches. Sure, you have to learn the terms
and acronyms, but I write user manuals for operators to telecom
administrator. So, other than learning the lingo, the words I write are the
same as I've always used. If you are writing for the switch manufacturer or
service carrier, your audience will probably be different than you are used
to -- more technically sophisticated with the subject, but at the same
time, also often called "Butt Set Bubba".
I have seen the multiple volumes of documentation for the switches that we
support. They are third person, passive, incomprehensible, poorly
organized, and in drastic need of a real writer. I hope you are going to
that company!
07:06 AM 6/14/99 -0600, you wrote:
>Name withheld upon request. Please reply on list.
>
>*************************************************
>
>I am considering making a switch to technical writing for a telecom
>company. My background is mainly software documentation, with lots of
>other side projects on various topics. I'd like input on the following
>questions:
>
