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: Non-Technical Technical Writers -Reply From:Chris Hamilton <chamilton -at- GR -dot- COM> Date:Thu, 7 May 1998 13:49:01 -0500
Obviously the answer to both of those questions is "no." But do you have to
have a substantial knowledge of object-oriented programming and distributed
systems to tell programmers how to use the distributed application server we're
currently working on? I know you do.
Some jobs require that technical knowledge, some do not. In terms of software,
I'm pretty technical for a technical writer. That's my discriminator. It
carries value in a lot of places, but not in all. I think anyone who looks at
it entirely one way or the other on these questions is missing the boat. In the
words of the great Al Borland, "the right tool for the right job."
Chris
Lisa Comeau wrote:
> Jason wrote:
> 1. Do you need to be an electrical engineer to tell someone how to use
> their VCR?
> 2. Do you need to be an expert in networking protocols and
> programming
> to explain to users how to use their e-mail programs?
>
> AMEN BROTHER! (excuse the yelling, I just REALLY agree)
> Lisa Comeau
> IS Super-User/Trainer
> Canadian Standards Association
> comeaul -at- csa -dot- ca
>
--
Chris Hamilton
chamilton -at- gr -dot- com
-------------------------
My views, not my employer's.
