Kent,
Thinking back to when I was a kid and had a problem my dad would hand
me the book/manual, if there was one for the thing giving me the
problem, and say "Look it up. I am not always going to be here to answer
all of your questions." Now that backfired on him when I totally
dismantled a new pocket radio he gave me, but then he said I had to put
it back together otherwise I had to pay for it out of my meager
allowance. But I learned a lot about soldering irons and a resistors
tendency to pop when too close to the heat.
I agree with the inquisitive nature aspect. You have to have that
desire to see "why".
John J. Boris, Sr.
JEN-A-SyS Administrator
Archdiocese of Philadelphia
"Remember! That light at the end of the tunnel
Just might be the headlight of an oncoming train!"
>>> "Brodie, Kent" <bro...@mcw.edu> 7/15/2010 9:48 AM >>>
My personal theory on this is, the typical type of troubleshooting
skills that a good sysadmin has, simply cannot be taught. It has to
do with your personality, how you were raised, your inquisitive
nature,
your willingness to take risks, and so on.
The *technical* tidbits, yes, can be taught ("ok, here's how you boot
a
*nix system into single user mode to begin a rescue..."), but the
above-mentioned investigative skills? You either got it, or you
don't.
_______________________________________________
Discuss mailing list
Discuss@lopsa.org
http://lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
