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.
> 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)
Alain: Furthermore, I am increasingly convinced that
the classic Top-Down approach (choice 2), while
laudable, is just not realistic. I now favour the
Bottom-Up approach, as do (some) researchers in
Artificial Intelligence and in Artificial Life (in
particular). Broadly speaking, it it the recognition
that software systems, despite their underlying binary
logico-mathematic formalism, are nonetheless systems
that are dynamic, non-linear, etc. And that these
complexities are difficult to fit into the old linear
ways of building systems.
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com
