>> Well now, there are basically two ways to do documentation:
>
> You already lost. If you're not documenting things that have no place in
> the source code to put the documentation, you've already failed at
> documenting your system.
That too.
I'm thinking about documenting a library API, but if you wrote an
application and want to write a user manual for it... the user isn't
going to give a damn about why you have to register a callback after
creating a button.
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|