And sometimes you've just got yourself an asshole.
It can be hard to tell which is which from someone's self-report. Presumably hoodoof (the original poster) has one or more people in mind which prompted hoodoof to write this, but from a one-sided view we really can't tell which is which.
Of course, in the end, I'm not aware of any career path which is populated solely by happy, healthy, well-balanced people that everyone loves to spend time with. Not even therapists or the clergy.
Working with other people means obvious disagreement, and sometime your disagreement will be productive and cause change, and other times it won't. Theres a lot of people who cross the fine line of productive discourse and unproductive disagreement though, and there's some people that seem to thrive on the other side of that line in this industry -- I imagine that's the attitude that a lot of people find off-putting.
I'm curious if you had coding standards (internally developed, or adopted from another party / standard) that stated best practice?
In my experience, an objective standard is really important in these discussions. If you did, and they wanted to avoid it, was it referred to? If you didn't, was developing a standard taken as a learning point to be adopted in the future, or not pursued?
Because someone wrote an SQL query with string interpolation of variables and no escaping. Why? Because the values at that time were actually coming from a limited set and were safe to provide that way. Yet I argued that it should be a prepared query anyway, so that we avoid it potentially exploding in the future.
Was he right that it doesn't matter at the time - yes. Would I be the annoying, stubborn, difficult person who knows better again in a similar situation? Yes! And I know some people will be angry about it while others will agree with me. That's life.