2 Jun
1999
2 Jun
'99
7:38 a.m.
1. Observe symptoms
2. Make predictions
3. validate predictions
4. If predictions do not pan out add this
to the observed symptoms and go back to step 2 or 1.
5. Repair bad part.
I find that most don't understand the importance of steps
2 and 3. They try to go from 1 to 5 and usually it doesn't
work. Step 2 does require that you understand what to
expect from each kind of failure.
If you read usenet and/or the questions being asked on CLASSICCMP,
you'll find that most folks can't even execute step 1 correctly. If
I had a dime for every time someone complained about some problem they
were having and didn't even bother to quote the command line they were
trying or the exact error message that resulted, I'd be a millionaire.
--
Tim Shoppa Email: shoppa(a)trailing-edge.com
Trailing Edge Technology WWW: http://www.trailing-edge.com/
7328 Bradley Blvd Voice: 301-767-5917
Bethesda, MD, USA 20817 Fax: 301-767-5927