*sigh*
<!--<br />
As with many conversations that I have with Colin, i have to chew it over in my head for a while, and then digest it before it sinks in. So yesterday I had a conversation outside with Colin as he smoked a cancer stick. I could tell he was eagerly awaiting our talk, because last week he asked me to think about how our relationship was going. So I picked out a few of the less painful points, and batted them around with him, and he seemed to be ok with it. But then again, I never know what he's really thinking. Eventually twists the conversation into a discussion on whether I like him or DeWayne better. Somehow I just got sucked back into high school. I didn't realize that this was some popularity contest. I've said it before, and I'll say it again, the man is all ego. At any rate, I wasn't about get drawn into a "who do you like best" conversation, so I just told him that their personalities were so different that it would be impossible to compare and judge, and that they were just too different. How can I ever even contemplate being honest with this guy when he sees it as a popularity contest?<br />
-->
Today one of our more quirky (where quirky is code for obnoxious) customers reports a problem where cvs log messages aren't appearing in bugs like they should. I spend an hour digging through assorted logs and determine that the reason the cvs log message doesn't appear is because they never activated the functionality for that cvs module. So instead of accepting that its user error across the board, this guy calls me and tells me that he's ordered all of his developers to stop using cvs until I can determine the cause for the two other incidents. Unbelievable. He's making me responsible for his team's lack of productivity, even though I've proven that the first occurance was user error. But it gets better. He's claiming that this breakage is caused by a service pack that he applied back on May 10, and he happens to casually comment that one of the patches failed to apply. I asked him why he didn't contact Support immediately when the patch failed, and his response was that he was too busy. Now our service pack documentation clearly instructs a customer to contact support immediately if there are any problems. At this point I poke around on his server and determine that all three of the instances of the cvs log not appearing in the bug all occured *before* he applied the service pack on may 10. So that proved that the service pack had nothing to do with it, and if anything was actually broken, it was broken for quite a while. This customer has a long track record of contacting support late in the day with urgent or critical problems that he's known about or a long time before hand but was 'too busy' to report. I ended up telling him that I wouldn't complete my investigation of his problem until tomorrow, and that it was his call whether he wanted to prevent cvs usage until that time. He didn't sound too happy, but he'll live. I was not about to stay late just because his users can't read instructions and aren't doing their jobs right.