RE: huh?

Subject: RE: huh?
From: Goober Writer <gooberwriter -at- yahoo -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Fri, 9 May 2003 04:23:41 -0700 (PDT)

It's great if an editor can cite problems in the
information itself, but I think we're confusing some
very critical roles here. Or maybe the business
climate is forcing us to get used to wearing too many
hats at once.

A technical writer should know the audience, purpose,
and subject of what is being authored. A technical
writer should be chasing down details and scrutinizing
them before committing them to a deliverable. A
technical writer should know the policies and
procedures surrounding the creation of the
deliverable, and should adhere to them.

A technical reviewer should be intimate with the
technology the deliverable is discussing, and should
be able to point out flaws in logic, misinformation,
vague information, and additional info that is
currently missing from the deliverable.

The technical editor should be reviewing for
logical/correct construction of the deliverable,
grammar, correct application of the policies and
procedures surrounding the creation of the
deliverable, and should offer suggestions on anything
else that doesn't seem to fit.

What are the policies and procedures I am talking
about? Defined style, template use, structure of
information, and process for publishing the

Those are my thoughts. They have worked for me thus far.

Goober Writer
(because life is too short to be inept)

Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.


Order RoboHelp X3 in May and receive a $100 mail-in rebate, PLUS
free RoboScreenCapture and WebHelp Merge Module.

Order RoboHelp today:

ATTENTION FrameMaker Users: Fill-out the following survey
to receive a chance to win a FREE RoboScreenCapture.

FM users only please:

You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit for more resources and info.


RE: huh?: From: Jean Hollis Weber

Previous by Author: RE: XP look-and-feel
Next by Author: Re: Fear and Loathing, Part 2
Previous by Thread: RE: huh?
Next by Thread: RE: huh?

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

Sponsored Ads