🚀 go-pugleaf

In article <1jnfejINNkg3@usenet.INS.CWRU.Edu> aa794@cleveland.Freenet.Edu (Pete Nofel) writes:
>   "We put off the documentation because we could let that slip with the
>least amount of pain."

>   We have a saying in our technical writing group: We're the people the
>engineers call in when they've only got $10 and two weeks left in the
>project.

>  Are we the only ones facing this kind of treatment?

Quote from the most recent copy of Intercom :

"Will the product development people ever get a clue about what it
 takes to write a manual? When I was young and naive, I thought I was
 the only technical writer in the world that learned about a new
 product two weeks prior to release."

You're not alone!

We're about to release an updated version of our software. In theory
my job on it should have been finished by yesterday (Friday).

I was still finding new things in the software on Thursday. "Oh yeah,
forgot to tell you about that one..."

I can offer little advice about what to do it with - speak to the
development manager and explain to her/him what your job entails.
Explain why you need time. Point out the benefits of getting technical
writers involved in the development process. Not onl do you get better
manuals but you often end up with a better product too.
-- 
    Thomas Beagle | thomas@datamark.co.nz           Work: 64 4 233 8186
 Technical Writer | thomas@cavebbs.welly.gen.nz     Home: 64 4 499 3832
   Wellington, NZ | Yes, I do have long ears, a black nose, and a tail.