|
After reading your story, I began to wonder about the other side of this. Did the code you wrote work in all cases? I certainly have seen (and, maybe been guilty of) cases where an algorythm is implemented thinking it's more efficient, better, whatever, and works for new cases, but doesn't pan out for the original usage.
If, however, it's the case that the guy just got his panties in a knot, fug-im. Though it would be nice, as the previous poster mentioned, to sit down and talk with him about it, in the real world that doesn't happen. Case in point: Right now I'm working on a tight deadline for improving performance for a customer. I'm rewriting tonnes of methods, simplifying algorithms, if I had to sit down with the original developer every time I did that I'd never meet my deadline.
Now, back to my original comment: We don't hear the other guy's side of the story. Is he the 'team lead', or is there code-ownership? For example: if you're the 'process queue' guy, and he owns the 'scheduling' stuff, then I could see his case.
|