Re: Value added by technical documentati

["Wilcox, John (Contractor)" <wilcoxj -at- WDNI -dot- COM>]

 ----------
From: Virginia J. Link

So this discussion leads me to my burning issue: where do technical
writers
belong in the development/testing/production phase?  If we have to
document/bandage bad UI and programming (and take the heat for manuals
that
are too big, too costly, too late, blah blah ad nauseum), don't we
really
belong in the picture long before the code is codified?
.
.
.
Whew!  (Head swiveling around back into place)  Sorry about that!  It
might
be apparent that this has been bugging me for a few years now.  Anybody
else
been in this situation?  Been there, done that?
 ------------

Nope.  You're clearly in unchartered waters, mate.  NOT!  Sounds all too
familiar.  However, I can say very appreciatively that my present job is
a veritable vacation compared to the previous five-year stint.  A lot
more money and a lot less stress.  So don't give up hope -- there is a
God!  My advice to you: Consider working in the real world instead of
for the state!  You're beating a dead horse!  They thrive on the stuff
you're trying to fix.

 TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot-  Send commands
   to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
  Search the archives at http://www.documentation.com/  or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html