Any given problem has a certain intrinsic level of complexity.  In the
solution of the problem, this complexity will be conserved:  if you dive in
with too little advance thought, your solution may become very complex by
the time it's done.  On the other hand, if you invest more in thought,
design, and preparation, you may be able to achieve a very simple solution
(the complexity hasn't gone away, it's become embodied in the sophistication
of the design).

In connection with our recent discussion, that investment certainly can take
the form of prototyping.  When I was working with Chuck, he'd typically go
through the following process:

1. Read the spec.  Assert confidently that it really isn't as complicated as
that, and write a very clever program that solves the essence of the
problem.

2. Enter a phase in which the customer repeatedly points out aspects of the
spec that have been ignored or omitted; in fixing these, the code gets more
and more complicated.

3. At some point, a full understanding of the problem emerges.  All the
previous code is thrown out and a new program emerges which represents a
simple, elegant solution to the *whole* problem.

Cheers,
Elizabeth

--
==================================================
Elizabeth D. Rather   (US & Canada)   800-55-FORTH
FORTH Inc.                         +1 310-491-3356
5155 W. Rosecrans Ave. #1018  Fax: +1 310-978-9454
Hawthorne, CA 90250
http://www.forth.com