There seems to be 2 discrete methodologies on hardware repair:
[1] The swap-jockey who will simply try a different part based on the problems logical point of origin.
[2] The diagnostician who has the means, time, and savvy to run a battery of tests and metrics.
While the latter is more professional and elegant, it can also prove to be less efficient, time-wise. Or so my thinking goes.
I know this attitude can carry over into the software realm as well - the whole troubleshoot and fix vs. reformat mentality.
So what's your style? Personally, I blend both methods, but I favor the diagnostician.
[1] The swap-jockey who will simply try a different part based on the problems logical point of origin.
[2] The diagnostician who has the means, time, and savvy to run a battery of tests and metrics.
While the latter is more professional and elegant, it can also prove to be less efficient, time-wise. Or so my thinking goes.
I know this attitude can carry over into the software realm as well - the whole troubleshoot and fix vs. reformat mentality.
So what's your style? Personally, I blend both methods, but I favor the diagnostician.