3 ms·
I love this title because this was exactly the response I got from a contractor who was hired as a Technical Lead of a team I had to work with. I found a bug i
by HeyLaughingBoy 16y ago
I love this title because this was exactly the response I got from a contractor who was hired as a Technical Lead of a team I had to work with.
I found a bug in a module they released to my team, created a series of about 5 steps to make it perfectly reproducible and contacted the team lead. He adamantly REFUSED to believe me. Told him how to reproduce it and his response was "I don't need to do that because I know it works fine." I pointed out that until the bug was fixed, I couldn't make progress because my code was dependent on theirs working, he suggested it was somehow my fault. 'K then. I found a way to reproduce the bug without any of my code running (they had written a simple external dialog to demo the module) and the guy still maintains that "there are no bugs in that code, I've been running it here for weeks. You must not know what you're doing."
If he wasn't 1,000 miles away I swear I would have gone over there and beaten him over the head with a stack of Knuth!
Finally I said screw it and went over his head. I knew his manager (who used to be a programmer) pretty well and explained the problem and how I was being stonewalled. He figured it out in less than a minute on the phone and told me how to setup their configuration file so it wouldn't trigger the bug and promised the bug would be fixed. And apologized as a bonus.
Not surprisingly, we had tons of problems later with them not properly testing a bunch of common error paths. Finally the TL pissed off the wrong person and got himself fired.
OK, this is a bit OT, but I needed that rant :-)