Troubleshooting problems is an ‘art’, not a ‘science’. Either you know how to do it, or you don’t. And, like any other “art”, you can’t teach it; you _can_ teach ‘mechanics’ that help people who have an ‘instinctive’ (for lack of a better word) grasp of the subject “do it better”. But the _ability_ has to be there in the first place.

It’s similaar to integral calculus — you have a result, and are looking for the question. (Remember how _hard_ integration was — until the ‘AHA!’ moment when, all of a sudden, it all made sense. And you were shaking your head wondering *why* you had so much trouble ‘getting it’.)

Troubleshooting is much the same. If you’ve seen “that” problem before, you have an idea of what -may- be causing it. And can start checking for the existing of each possible ‘what’ that you know about. With experience, you know _which_ “what” is most likely and to start there. Also, what additional_ things to check, to narrow down the list of ‘possibles’.

Copiat cu nerusinare dintr-un e-mail de pe NANOG, insa e cred ca cea mai buna explicatie de ce unii oameni pot sa faca troubleshooting si altii nu, si cel mai important: de ce nu poti sa inveti efectiv pe cineva sa faca troubleshooting.