June 9th, 2004, 07:12 PM
|
|
|
Re: The future of PBW - a call to arms
Quote:
Originally posted by Gandalf Parker:
...
A) programming from the top down. The menu choices are written, the sub-routines ironed out, often results in one huge program in one specific language, using the system to answer a need is the Last consideration
B) designed from bottom up, system answers are put in place first, then routines to access them, finally they are put together under menus
...
|
I would have thought that B is the best model for anything that's going to be built by a distributed team. And if we're talking about project structure and development style, then I'd like us to aim at a sort of RAD style prototyping + incremental updates approach rather than specifying an all bells-and-whistles PBW and trying to build it in one big go.
Quote:
and Roanon wrote...
Yes please.
I have been (also?) excluded from the exclusive tesco-picked circle of first-hand designers (I guess too much professional experience ) and don't know if I have made my point clear enough to whoever decides about PBW future that another system with the same eventually unmaintainable structure as the current system might not be desirable.
|
It would probably be good if we could avoid the paranoia and bickering quite this early in the project ... 
Mark
[ June 09, 2004, 21:17: Message edited by: Mark the Merciful ]
|