nanog mailing list archives
Re: Teaching/developing troubleshooting skills
From: "John Neiberger" <John.Neiberger () efirstbank com>
Date: Mon, 28 Jun 2004 08:18:02 -0600
It's also important that one avoid: * The faulty assumption there is but one problem * Incorrectly-formed causal relationships (NANOG-L has some examples of these) * Making too many changes in one iteration * Attempting to tackle a system with more unknowns than are absolutely necessary.
These words should be hanging on a wall in every IT department. You wouldn't believe how many times I've had to gently correct someone because of these mistakes, particularly the first two. John --
Current thread:
- Teaching/developing troubleshooting skills Pete Kruckenberg (Jun 24)
- Re: Teaching/developing troubleshooting skills Jon R. Kibler (Jun 24)
- Re: Teaching/developing troubleshooting skills Bruce Pinsky (Jun 24)
- Re: Teaching/developing troubleshooting skills Darrell Greenwood (Jun 25)
- Re: Teaching/developing troubleshooting skills Edward B. Dreger (Jun 26)
- <Possible follow-ups>
- RE: Teaching/developing troubleshooting skills Larry Pingree (Jun 24)
- Re: Teaching/developing troubleshooting skills John Neiberger (Jun 25)
- Re: Teaching/developing troubleshooting skills John Neiberger (Jun 28)
- Re: Teaching/developing troubleshooting skills Michael . Dillon (Jun 28)
- Re: Teaching/developing troubleshooting skills Bruce Pinsky (Jun 29)
- Re: Teaching/developing troubleshooting skills Eric Brunner-Williams (Jun 28)
- Re: Teaching/developing troubleshooting skills Michael . Dillon (Jun 28)