[In a message from Bucky Carr to Harry Hickey ]
 BC> I sure see what they mean.  I have a VB app that continues to grow,
 BC> then I stop for a few days and write some documentation, then go back
 BC> to coding, etc.  Trouble is, as the book says, *I*, as a programmer,
 BC> won't ever be able to do justice to the documentation...
I think the biggest problem with doing this is, after working on the
code for so long, that writing the documentation for it just tedious,
and not at the top of the list. Another problem is, what seems obvious
to you as the programmer is not obvious to the users at all. Want to
know what to put in the docs? Just give your program to someone who
isn't particularly computer literate. They'll find the holes, and ask
some of the darnedest questions.
.                         pat.pridgen@svis.org
.                          La Grande, Oregon
*SignIt 2.x #001* 
... Documentation - The worst part of programming.
___ Blue Wave/DOS v2.30
--- Maximus 2.02
---------------