Today William Case did spake thusly:
Anne, if I may take the liberty of whole heartedly agreeing with you
Les's proposal sounds like a MicroSoft proposal.
In an ideal world, you'd create an application dummy. Get prospective
users to use it in various scenarios (UAT). Watch them. Take that feedback
on board, develop a sensible set of defaults, then develop a way (user
prefs or something) to override all those defaults. Then do another UAT
cycle, clean up any issues discovered, and that's it. Voila, best of
both worlds.
This is how software *should* be developed. Programmers all too frequently
forget that they are servicing the user, not telling them what to do.
--
Scott van Looy - email:me@xxxxxxxxxxxxxx | web:www.ethosuk.org.uk
site:www.freakcity.net - the in place for outcasts since 2003
PGP Fingerprint: 7180 5543 C6C4 747B 7E74 802C 7CF9 E526 44D9 D4A7
-------------------------------------------
|/// /// /// /// WIDE LOAD /// /// /// ///|
-------------------------------------------
Bathquake, n.:
The violent quake that rattles the entire house when the water
faucet is turned on to a certain point.
-- Rich Hall, "Sniglets"
