Re: Try selling the sizzle of what you do.

[John Posada <john -at- tdandw -dot- com>]

Until I develop the ability to tell the future, I take the position that
what I have in my hand is what will go out the door, and that's what I
write. If it changes tomorrow, then tomorrow I'll make the change. I've been
burned too many times by production who pretty much said...don't worry about
it. We're fixing it now...it will be in the next build. The build came, the
change didn't.

>>>Always how it currently works.

>>Well, the way it will work when the product goes out the >>door.  If I
know that there is a bug report, and that it is >>assigned to a programmer
who is going to fix it next week, >>and that the product will not be
released until the product >>works the way I have documented it, why should
I change the >>documentation so that it reflects the incorrect behavior, and
>>then change it next week to reflect the correct behavior.

Because in my experience, it often doesn't happen.

John Posada
Senior Technical Writer
john -at- tdandw -dot- com



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
Buy or upgrade to RoboHelp X3 today and receive the WebHelp
Merge Module for FREE ($299 value). RoboHelp X3's all-new
features include conditional text, completely re-engineered
printed documentation output, Context-sensitive Help Toolkit,
single-source layouts, and more!
Order online today at http://www.ehelp.com/techwr-l


---
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
http://www.raycomm.com/techwhirl/ for more resources and info.