What do I mean by "invisible proxy"? Well, here are some examples (AKA culprits!):
I think it's important to note that in this context I'm talking about troubleshooting rare problems. If this was a common problem, you'd have fixed it already; you wouldn't be searching for invisible proxies or discovering new layers, because the visible/tangible layers are so much more discoverable. Why check your firewall settings when your network cable is unplugged?
Rare problems require a different mindset from common problems.
Trust nothing; start looking at your own assumptions and (of course) anyone else's assumptions; look to the Golden Rule of Troubleshooting. Double-check your earlier work. Double-check your double-checking to be sure you covered everything. Get some rest, then come back and double-check your double-double-checking.
Double-check everyone else's work (yeah, I know).
When doing advanced troubleshooting, it's important to keep in mind that a) with computers, there is always a logical answer (even if that answer is "the hardware is intermittently breaking), b) you've already isolated every single layer possible, and c) it's now time to stop believing people and now time to start checking their assumptions. An important corollary to part c is you must also turn a distrustful eye towards yourself. Did you check everything? Are you sure? Before you make that accusatory phone call, are you 100.0% sure?
Remember Me
a@href@title, b, blockquote@cite, em, i, strike, strong, sub, sup, u
Powered by: newtelligence dasBlog 2.2.8279.16125
Disclaimer The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.
© Copyright 2010, Peter Seale
E-mail