Re: Developer Documentation

Subject: Re: Developer Documentation
From: John Gilger <jgilger_it -at- NV -dot- DOE -dot- GOV>
Date: Tue, 23 Mar 1999 08:27:09 -0800

I have to agree with Jane on this one. I don't recall having the choice
of what I wrote. If the boss wants a doc written or edited, that is
what I get paid to do.

I am amazed at the attitude of some tech writers that they only write
user manuals.

Variety is the spice of life. It is a lot more interesting to have a
part in design, documentation, marketing, and whatever else needs to be
written. Heck, I've even edited/rewritten letters for the CEO.

I guess that I am more of a wordsmith that likes to work with words than
a technical writing specialist.


-----Original Message-----
From: Jane Bergen [SMTP:jbergen1 -at- EARTHLINK -dot- NET]
Sent: Tuesday, March 23, 1999 8:11 AM
Subject: Re: Developer Documentation

Scott Wahl writes:

>I would recommend against volunteering to write and format
Whoaaaaa. Not all technical writers write only customer
While I wouldn't recommend that tech writers WRITE the developer
I do think it's a good idea to volunteer to edit them. And edit
content, organization, and style as well as for grammar and
This could have several benefits, but primarily the ones below:

From ??? -at- ??? Sun Jan 00 00:00:00 0000=

Previous by Author: Re: What is a document?
Next by Author: Re: CSS with Netscape
Previous by Thread: Re: Developer Documentation
Next by Thread: Re: Developer Documentation

What this post helpful? Share it with friends and colleagues:

Sponsored Ads