[102483] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Interpersonal skills needed for Network Engineers

daemon@ATHENA.MIT.EDU (Gadi Evron)
Sat Feb 16 23:17:22 2008

Date: Sat, 16 Feb 2008 22:15:24 -0600 (CST)
From: Gadi Evron <ge@linuxbox.org>
To: Joel Jaeggli <joelja@bogus.com>
cc: Bill Nash <billn@billn.net>, Kim Onnel <karim.adel@gmail.com>,
        NANOG list <nanog@nanog.org>
In-Reply-To: <47B77BB9.90807@bogus.com>
Errors-To: owner-nanog@merit.edu


On Sat, 16 Feb 2008, Joel Jaeggli wrote:
>
> There is a topical tutorial for people attending nanog 42 sunday afternoon...
>
> http://www.nanog.org/mtg-0802/zwicky.html

To emphasize the OT but important point..

I wish medical doctors were taught this as well. Although a ghastly 
over-simplification, most M.D.'s any of us will ever meet are technicians. 
Very advanced and qualified ones, but technicians.

They:
1. Analyze what the problem might be by examining sympthoms.
2. They debug, one by one, by likelihood.

Analysis varies depending on the M.D. Debugging shouldn't.

Some never learned how debugging works. One example is a friend of 
mine whose doctor tried to give 6 different medications at once to solve 
the unknown problem.

My friend's question was, after asking why not try one by one (he wasn't 
near death, so this wasn't an emergency response situation):
"What if my sympthoms go away, which medication(s) do you stop?"

Some of us may be more open to examples from realms not relating to 
routers and switches. :)

 	Gadi.

--
*FART*
    -- Avi Freedman to Gadi Evron in a Chinese restaurant, Boston 2007.

home help back first fref pref prev next nref lref last post