Isn't there a build that's breaking somewhere because of this? It sounds like you're describing symptoms of a shop that's not set up quite right. You say you'

Isn't there a build that's breaking somewhere because of this? It sounds like you're describing symptoms of a shop that's not set up quite right. You say you've got a guy making breaking changes to shared code, and not fixing up the references. That's something that should rapidly self-report in the form of a broken build. The dev in question will get the big flashing "cone of shame" left on his desk, be assigned the task of "build master" for a while, and have his commit rolled back. This sort of thing runs automatically (apart from cone delivery) at most shops. You also seem to have a bit of a "code ownership" thing going on at your workplace, since you mentioned "your code" and "his code" a few times. Gotta get rid of that. Let your buddy change whatever he likes. No skin off your nose, so long as he fixes up the references. It sounds like there must be some silly policy in place that's either not letting him do that or not requiring him to. Gotta fix that too. Naturally, these are technical fixes that don't address the underlying social problem. Fortunately, that's the only kind of fix that an Aspergers Sociopath developer of the type you describe will respond to. Make the rules say that he shouldn't be such a dick, and he'll adjust his algorithm to at least stop being that particular flavor of dick. Good luck!