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:"Campbell, Art" <artc -at- NORTHCHURCH -dot- NET> Date:Mon, 14 Jun 1999 09:49:58 -0400
I've found the main difference is hardware writing vs. software writing, not
telco industry vs. software industry. Telco is very much equipment-based,
the
software is there mainly to make the equipment do tricks. ;-) There are
exceptions
as you move toward the end user, bot for almost anything beyond the desktop,
there's hardware directly involved.
There is a new language to learn -- lots of new acronyms and such, but
Newton's Telecom Dictionary should answer most of those questions.
With the possible exception of heavily style-policed documentation styles
used by
Bleacher and the BIG companies, if you can write tight, write bright, and
write right, you won't have any problems in either field, or moving back
and forth between the two.
Art
Art Campbell
Technical Publications
Northchurch Communications
Five Corporate Drive
Andover, MA 01810
978 691-6344
-----Original Message-----
From: Anonymous User [mailto:anonfwd -at- RAYCOMM -dot- COM]
Sent: Monday, June 14, 1999 9:06 AM
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Subject: FWD: Telecomm writing vs. Software writing
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:
1. What qualities are needed to succeed in the telecom environment? Do
they differ from those needed in the software environment?
2. How much of an engineering mindset do you need?
3. Is it possible to transition back to software documentation?
4. Anything else telecom writers can offer that would be helpful in
making a decision in this regard.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Message forwarded on request. Please reply on list.
