Comment Re:Yes we should but... (Score 1) 291
Troubleshooting is a skill applicable to, and learned in, far more than the narrow domain of coding. Your experience is biased by the crowd you hang out with in your chosen profession.
But any good mechanic (taking that as a generic term for electrician, plumber, etc also) is a good troubleshooter/problem solver, ditto any other expert in their chosen field (doctors, lawyers, salespeople, etc). It's a skill you need to be a good programmer, but it's a skill you need to be good at anything. How do I isolate the symptom? What is the real problem? What can I do to fix it? What can I substitute or change if I don't have the right part (library, API) to fix it as is?
I've seen plenty of coders who weren't that hot at troubleshooting (especially if it required some out-of-the-box thinking). I don't think coding teaches that skill, but it may well exercise it and make it stronger if it's already there.