Re: Versatility - how much is a good thing?
Title: RE: Versatility - how much is a good thing?imho, this definition of TW is pretty limited.
Instead, I tend to think that TWs produce information for an end-user. So yeah, just about everything listed in the original post is one form or another of technical writing (except maybe for network diagrams, and there could be arguments for including them in the tw field also).
Dan Roberts
droberts -at- isogon -dot- com
> -----One response-----
> you're being used
> as a glorified typist. A technical writer produces customer-oriented
> documentation that is integral to the product. Period.
>
> -----Original Message-----
> > I am expected to produce, on very
> > short notice, HR policies, user manuals, training documentation, network
> > diagrams of all shapes and sizes, system documentation, business process
> > flowcharts, internal IT reference materials, project plans & scope
> > documents, Y2k testing methodology, architecture documents, and audit
> > responses, as well as serve as an IS project manager, contact person for
> > outside departments, and general department "duct tape" for whatever
> > needs fixing. I'm usually expected to make recommendations and
> > contribute content to the material that I research and document, as
> > well.
Previous by Author:
grammar term
Next by Author:
Re: grammar term SOLVED
Previous by Thread:
Re: Versatility - how much is a good thing?
Next by Thread:
Re: Versatility - how much is a good thing?
Search our Technical Writing Archives & Magazine
Visit TechWhirl's Other Sites
Sponsored Ads