Re: Writing Technical Documentation

[Elizabeth Ross <beth -at- vcubed -dot- com>]

Hi Jill!

Yep, that's technical writing all right. But I must ask why would you want
to bow out of tasks that would allow you to increase your skill set, thereby
expanding your wage range? There are tons of tech writers who know how to
document software. There are not nearly as many doing the tasks you
describe, which can be a bonus.

As always, if it's not the direction *you* wish to move in, then you should
pass, whether or not the tasks are considered "technical writing".

My $.02 Cdn.
-- 
Elizabeth Ross
Senior Technical Writer, V3 Semiconductor Corp.
beth -at- vcubed -dot- com          http://www.vcubed.com
Cogito cogito ergo cogito sum.


> From: "Kenny, Jill" <jill -dot- kenny -at- corp -dot- bellsouth -dot- net>
> Reply-To: "Kenny, Jill" <jill -dot- kenny -at- corp -dot- bellsouth -dot- net>
> Date: Tue, 23 May 2000 13:23:40 -0400
> To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
> Subject: Writing Technical Documentation
> 
> I'm being asked to write and assist in writing highly technical documents
> for our software development center. These documents include technical
> design docs, architectural overviews, application roadmaps, and development
> methodology descriptions. Do these types of documents fall under the
> category of technical writing? And if not, any suggestions on how to
> gracefully bow out of these tasks.
> 
> In my years of technical writing, I have always been involved in developing
> user-end documentation, i.e., help files, user manuals, etc. So this is
> completely new to me.
> 
> Jill Kenny
> Bellsouth.net
> 678 441-7356
> email: jill -dot- kenny -at- bellsouth -dot- com