At 12:12 PM -0800 on 11/19/99, Alain Farmer wrote:
>Anthony: BugTracker is nice, but you should add
>directions which btn does what, and what info is
>needed to complete forms, etc. Some btn names are less
>than self-explanatory.
I think this was Uli's line.
>
>> Documentation? Yes, I should add that. Dang it, it's
>> not even beta :)
>
>Alain: What a classic programmer dilemna this is.
>
>1. Do I spend most of my time coding intuitively, then
>document my resulting work later? And, consequently,
>documentation always lags ... Why wait for the docs to
>be ready to release the software?
>
>2. Or do I design everything on paper beforehand and
>maintain this documentation during my development
>work?
>
>Alain: I know the second choice is the textbook answer
>to this dilemna but, in real life, it is more often
>the first tactic that is used instead, eh! (myself
>included)
I'd say the first tactic is better. Far better. I find it silly to write
TFM before there is software to write it about -- you'll just end up
re-writing the manual anyway.
But, even better is the side-to-side method. Think Differently <g>.
