I agree with Kent here, but I think some of it can be taught by putting the person in the situation. I would set up a machine and break a few things on purpose and then turn the person loose with a vague (end-user type) description of the problem. I think doing this repetitively will help to build those abilities.
That being said this will only help to strengthen those skills if they are there! On Thu, Jul 15, 2010 at 6:48 AM, Brodie, Kent <bro...@mcw.edu> wrote: > 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. > > > > (My $0.02…) > > > > --------------------------------------------------------------------- > > Kent C. Brodie > > Department of Physiology > > (and) Human and Molecular Genetics Center > > Medical College of Wisconsin > > bro...@mcw.edu +1 414 955 8590 > > _______________________________________________ > 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/ > >
_______________________________________________ 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/
