Re: Documenting "touchy" applications? (take II)

[John Posada <jposada01 -at- yahoo -dot- com>]

> But I'm still not sure why your developers can't simply code the
> script so
> that it works from anywhere. Nobody knows the code like they do,
> and if they
> can't press the proper buttons so the user doesn't have to, it
> seems to me there's a bigger problem than how to document 
> the procedure.

Let me put this tactfully...

The programming project is being managed by an outside "big-bucks"
consulting company..so big, they have PGA Golf Tournaments named
after them. They are behind...very behind. Everytime someone says
"but it should work here too", their response is "It's not in the
requirements documentation (which they wrote), we'll classify it as
an enhancement for the next release (when we won't be around to worry
about it)".

Does that make it any clearer?

=====
John Posada, Senior Technical Writer
Current gig ending 4/15
Resume: http://www.tdandw.com/Resume_Posada_022202.doc
mailto:john -at- tdandw -dot- com, 732-259-2874

__________________________________________________
Do You Yahoo!?
Yahoo! Sports - live college hoops coverage
http://sports.yahoo.com/

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
PC Magazine gives RoboHelp Office 2002 five stars - a perfect score!
"The ultimate developer's tool for designing help systems. A product
no professional help designer should be without." Check out RoboHelp at
http://www.ehelp.com/techwr
---
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.