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: Re; Description From:"Parker, Cassandra M. (EXCH)" <CMPARKER -at- INTERMEDIA -dot- COM> Date:Mon, 9 Mar 1998 19:06:08 -0500
Sawyer,
I agree with comment below and again, we need more info.
>----------
>From: Sawyer[SMTP:sawyer91 -at- BELLATLANTIC -dot- NET]
>Sent: Monday, March 09, 1998 3:32 PM
>To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
>Subject: Re; Description
>
>I need a description so I'll know what is expected of me when I show up
>for work Monday. I'm working for a company that is automating training
>programs at an Army base. I am the only writer. I've done some research
>so I know basically, I think, what I'll be doing.
>Cathy
>
>> "Description of a technical writer" is WAAAAAY too broad. What kind of
>> writer (software, hardware, medical, scientific, oil and gas, and on and
>> on)? Then what are "basics" (online, paper docs, engineering specs,
>> release notes, etc.)? Do you want a description for someone who works in
>> a one-writer startup or a large, structured environment with lots of
>> other writers (the descriptions would be very different)?
>>
>> Next question, what do you want it for? Is it to use as a guideline in
>> your company, to put on a resume, to use when placing an employment ad,
>> etc.? The purpose makes a difference, too.
>>
>
>
>
>
