I agree (mostly) with all that Bruce writes except for the following.

On 10 Apr 98 at 16:53, toback2 wrote:

> Only after I've come up with a solution do I start deciding what
> hardware

My experience has been that the absolute hardest part of systems
design is pinning down exactly what is the problem that you want to
solve.  Once that is accomplished, the solution is usually blindingly
obvious.  The trick is in pinning down the problem.  Sometimes that
simply proves to be beyond the capacity of the people involved.

The pity is that many (most) automation projects commence design and
coding before the problem is properly identified.  From those faulty
 decisions to proceed come most of the memorable horror
stories regarding computer systems' waste, futility and failure.

So I would rephrase Burce's line to say:

> Only after I've determined the problem do I start deciding what
> hardware

Regards,
Jim
---
James B. Byrne                  Harte & Lyne Limited
vox +1 905 561 1241             9 Brockley Drive
fax +1 905 561 0757             Hamilton, Ontario
[log in to unmask]           Canada  L8E 3C3