Msg: 5352 *Conference*

08-19-94 18:48:30

From: RICHARD HANSON

To : MARY ANN SCHAFER

Subj: REPLY TO MSG #5351 (PROBLEMS)

----
I've been sitting on the side lines, reading the messages between you and
Comet, and I've come to the conclusion that your Model T to server problem will
not get solved if you continue along these lines.  It pains me to watch this
process.  Nothing in communications should take so long.

Of course, you might stumble onto the solution but it would be sad if you fail
to understand the underlying cause.  Thus, you will never be sure if the
problem is solved, and will walk away with nothing learned--no tools for the
future.

Perhaps it's time for the ... old ... scientific method !!

1) Start by drawing a diagram of the components.  Listing the hardware,
software and people involved.  You might not know all the parts in the puzzle
at this moment but that does not matter--they will present themselves as you
progress.

2) Access your knowledge about each component or process, then draw conclusions
about what works and what does not, based on your knowledge at that moment.
Again, knowledge is the direct result of the problem solving process.
Knowledge grows as you solve problems.

3) Formulate questions, and postulate answers and their meanings.  This will
give you a basis for comparison as you stress the system and isolate the
variables.

4) Isolate variables as you answer your questions.  It's really important to
trust each component in the system.  If you don't isolate each component to
test its worth, you can never trust it in the system.  Do not ASSUME!

5) Go back through steps 1 through 4 over and over until the solution presents
itself.

Hope this helps.  -Rick-