Hello Everyone,
I am looking for defining what are skills needed in people that will work in an ISP’s operational/NOC environment as Network Engineers.
In my humble experience, i have came across people that i just feel they are not right for such technical jobs, people would act and take their golden fingers to the devices without logic and others who has more of a structured approach to solving problems and thinking, some that will crank under pressure and just loose it and others who will act rationally.
Please correct me if i am wrong and if you believe such skills could be gained by time/training?
Maybe the above doesnt really need to be there for others in the development/engineering departments where more of studying and analysis skills are required, please correct me if i am wrong.
Private msg me if needed.
Thanks,
Kim
I think you're talking very generally about the 'cowboy' type of operators who will reboot first, and then troubleshoot if that doesn't fix it. There are also the territorial types who feel threatened in the face of outside ideas or questions.
Speaking as a volatile loudmouth (in recovery), I do think that interpersonal skill training, or at least practice, is useful for folks to be able to inter-operate both with other people, and other network operators. The single most useful troubleshooting skill anyone can bring to the table is a good pair of ears and a willingness to use them. With that as a base, you can move on to good teamwork and best practices.
As cliche as it may seem, I readily recommend 'Negotiating for Dummies' as reading for anyone who doesn't want to be the person that no one can work with. It works great when given as an anonymous gift, too.
- billn
Kim Onnel wrote:
<snip>
In my humble experience, i have came across people that i just feel they are
not right for such technical jobs, people would act and take their golden
fingers to the devices without logic and others who has more of a structured
approach to solving problems and thinking, some that will crank under
pressure and just loose it and others who will act rationally.
The Executive Summary:
You know those techs that are easy to understand,
and communicate so effectively,
almost alway seeing things your way ?
Those are the sycophants, Jungian type "E's".
You know those techs that always seem to
be talking over your head, and telling you things
don't work the way you think, always screaming caution ?
Those are you *real* techs, Jungian type "I".
Why can't most managers figure this out ?
See: Alpha Male Syndrome, by our friends at Monster.com
(Kate Ludeman, PhD, and Eddie Erlandson, MD)
http://www.alphamalesyndrome.com/
:-P
</noise><signal>
Proof read, and corrected.
* sigh *
time to call it a day. :-\
R. Irving wrote:
There is a topical tutorial for people attending nanog 42 sunday afternoon...
http://www.nanog.org/mtg-0802/zwicky.html
Bill Nash wrote:
'Hi, I'm Bill.. and I took down the network.'
"Hi Bill!"
- billn
Can somebody please take Audio or Video captures if possible please.
Thanks,
Kim
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.