2 ms·
> > People "know it when they see it" without necessarily being able to define it. > That path leads to hell. That's why they pay us the big bucks. If people
by barrkel 11y ago
> > People "know it when they see it" without necessarily being able to define it.
> That path leads to hell.
That's why they pay us the big bucks.
If people could define their problems well enough without iterative design, waterfall development would be a success story and all software would be outsourced to the lowest bidder.
- catnaroek 11y agoThat's wrong. It's perfectly possible to define your problem well, and still require an iterative process to find a good solution.
- barrkel 11y agoThe requirement for an iterative process is what I mean by "oracle"; it's the thing that tells you how far off you are on this iteration, and how to change your heading for the next iteration.
- catnaroek 11y agoThat's a rather weird use of the term “oracle”, which normally means “a black box that solves a decision problem in a single step”. Normally, to decide whether you've achieved your goals, you don't use a black box - you use performance metrics that you've defined yourself (and thus can't claim not to understand).