*background* SC works for a fairly large bank and is in charge of their computer storage. (Fun Fact: He's a "Vice President" at the bank. But at banks and insurance companies, just about everyone is; title inflation is rampant.) In a previous life, he was a semi-technical big-shot a storage networking company. Recently he was a consultant for another one of my customers and he was an SC there too. (The other customer realized what a useless biased ass he was and pushed him out.) He probably got his current job through the 'ol boys network, since it can't be because he has any freaking clue what he is doing.
I tangled with him at his last employer, and now I get to deal with him again.
*end background*
SC is having performance problems. While there *may* be a bug somewhere in our gear, we *know* that he is overloading his disk drives. Badly. However, he is convinced that *the* problem is with his networking equipment made by *Vendor* but sold by us.
He thinks, because he was familiar with the protocols years ago, he can B.S. his way into... well, I don't know what his goal is. He's trying to score points by trying to invent scenarios he thinks we won't understand, or at least won't know enough to disprove. (i.e. Well, if the blargle bit is shifted left by three, the foozlebat latency increases by a factor of two on the mumblefratz command stream.)
He picked the exact WRONG Engineer (yours truly) to argue with about this. I know enough that when I presented my conclusions to the other people working the issue, the vendor pretty much said: "Um... Yeah, whatever SirWired said." I know more about troubleshooting this particular corner of the protocol stack than just about anybody else in the entire industry, no matter who they work for.
I'm REALLY looking forward to taking this guy apart on Monday. I don't think he remembers my name from the last time I made him look like an idiot. I give it a 50/50 chance that he still won't believe me, and will request more evidence (which I would already have if he had done his job properly), and I'll get to use said evidence to make him look even more stupid.
SirWired
I tangled with him at his last employer, and now I get to deal with him again.
*end background*
SC is having performance problems. While there *may* be a bug somewhere in our gear, we *know* that he is overloading his disk drives. Badly. However, he is convinced that *the* problem is with his networking equipment made by *Vendor* but sold by us.
He thinks, because he was familiar with the protocols years ago, he can B.S. his way into... well, I don't know what his goal is. He's trying to score points by trying to invent scenarios he thinks we won't understand, or at least won't know enough to disprove. (i.e. Well, if the blargle bit is shifted left by three, the foozlebat latency increases by a factor of two on the mumblefratz command stream.)
He picked the exact WRONG Engineer (yours truly) to argue with about this. I know enough that when I presented my conclusions to the other people working the issue, the vendor pretty much said: "Um... Yeah, whatever SirWired said." I know more about troubleshooting this particular corner of the protocol stack than just about anybody else in the entire industry, no matter who they work for.
I'm REALLY looking forward to taking this guy apart on Monday. I don't think he remembers my name from the last time I made him look like an idiot. I give it a 50/50 chance that he still won't believe me, and will request more evidence (which I would already have if he had done his job properly), and I'll get to use said evidence to make him look even more stupid.
SirWired
Comment