So here's the deal. Yesterday a problem arose at the company I work for. The program was related to software that I had written, and therefore a responsibility of mine to take care of. Unfortunately for me, the problem was very inconsistent, affecting only certain users of certain browsers part of the time. Internet explorer was the only browser affected, and my particular Internet explorer was not displaying the problem, therefore making it 5 times as hard (seeing as though I was trying to diagnose a problem I could not see, much less duplicate). Finally I found coworkers who were having the same problems, and was able to do slight testing on their machines (only part of the time tho, remember that the problem was very inconsistent). After having exhausted the possibility that I had actually introduced a regression error in a previous update, I decided to take a step back and find out where the similarities arose between the seemingly infected computers. What I *FINALLY* came up with (thanks to Tanya my coworker for her brilliant suggestion), was that it had to be caused by something on the individual's computer (which in this case, it was patches issued by Micro$oft). Apparently Micro$oft issued a patch that was defective, creating a situation that would affect many webservers out there. We fixed it so that our webserver was not affected by Micro$oft's incomptetancy (we run a unix webserver... and were still affected by this crap). 24hrs from the realization that we had a problem to the actual solution (that took M$'s incompetency into account). Voila, case closed, thank you M$ for trying to get me fired. May your next attempt be as unsuccessful as this one.
Posted by kposey at February 13, 2004 02:40 PM | TrackBackHey buddy
I know I'm late but congratulations on the wedding. Being married is so cool, though at times, but much better than not. catch you later.