> n...@cam.ac.uk wrote:
> > Absolutely.  Analyse first.  Design second.  Code and debug third.
> > Every good engineer knows that rule!

> > You need to run a couple of simple tests to check that your code
> > matches your analysis, and there isn't a major flaw in the analysis
> > itself, but you don't need to do more than that.  The main testing
> > comes where you can't analyse the problem, or where you suspect the
> > analysis may be unreliable.

> Which, in practice, is all the time. I mean, have _you_ ever spoken to a
> customer who knew what he wanted, completely, correctly, and up front?
> I know I haven't.

> Richard