On Mon, 22 Jan 2007 20:17:30 -0600, decaturtxcowboy
<nope_none_@nowayspam.com> wrote:

>Fixing the problem is usually easy...finding what the problem is hard.

Nope. Both fixing and finding the problem are trivial compared to
assigning the blame. No problem can be solved unless a culprit is
found. In general, it's best to blame someone that is no longer
around or available to defend themselves. Certainly, never blame
anyone that is needed to repair the problem. Interrogation of the
innocent is also a necessary skill. Grilling them for what they
changed, even after they insist that they didn't change anything, is a
fundamental requirement before attempting any serious troubleshooting.
Often, it is difficult to obtain a blame consensus depending on how
the participants are polarized. For example, it is difficult to blame
a Windoze crash on the company Linux faction. Similarly, it is
difficult to blame a hardware failure on a programmer. The real
problem is that there has been little investigation and almost no
publications on this very important aspect of troubleshooting. If
certification classes included more exercises on finger pointing, buck
passing, interrogation, and office politics, troubleshooting will be
greatly facilitated.



--
# Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
# 831-336-2558 jeffl@comix.santa-cruz.ca.us
# http://802.11junk.com jeffl@cruzio.com
# http://www.LearnByDestroying.com AE6KS