RE: Content Moratorium

[david -dot- locke -at- amd -dot- com]

I used to work in a place that the point where we had a functional
application would start creating daily builds. We could install these on our
test machine. They might be buggy enough to require a reinstall of the
operating system, so we were not supposed to load applications on production
machines. 

Using a daily build and the RH What's This Help Compiler, you could see
everything that changed from one build to the next. We did not rely on the
programmers to tell us what was or did change. Doing this allowed us to stay
ahead of the curve. It did help, however, to know when a new piece of
functionality was expected. And, we had enough meetings with the developers
and the rest of the product team not to be isolated or out of the loop. 

David W. Locke



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems 
Available 4/30/01 at http://www.devahelp.com or info -at- devahelp -dot- com

IPCC 01, the IEEE International Professional Communication Conference,
October 24-27, 2001 at historic La Fonda in Santa Fe, New Mexico, USA.
CALL FOR PAPERS OPEN UNTIL MARCH 15.  http://ieeepcs.org/2001/

---
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.