Tukukkk

A few months ago, I was temporarily (until the end of this year) put on another team. There is one other developer, and we've been struggling in our day-to-day interactions from day one. He's not used to working with someone else, nor to teaching/explaining code, nor to peer-reviews or working with git and merge requests. The entire team is just transitioning to working Agile/SCRUM, and he seems reluctant to make that change.

We both seem to be struggling with a generation gap. At the same time, I probably have been wrong by not addressing this earlier and just deciding to suck it up for a few months, leading to a bigger blow-out than immediately addressing every small thing would have done.

A few weeks ago, despite my best intentions to just sit this one out, I blew stuff up (we had a row about adding dead code to the code base and some scope creep, both of which I was refusing to do), leading to him and his work being scrutinized by other developers and managers.

I've spent quite some time that week having talks with him, the scrum master, other senior developers, managers and product owners. Overall, I came out relatively unscathed, and I don't think this has damaged my career in any way, nor do I feel threatened it may at any later point.

But I've burned some serious bridges with this co-worker it seems. I get the impression he's trying really hard to find some fault in me, some flaw that he can use to 'even out' what happened between us. Something he can use to create a situation like I did that week, but in reverse, with me being the one being scrutinized by managers and other developers. The last straw for me was when he accused me of doing something that version control shows I had no hand in. I've already again contacted my manager and let them know about this; they advised me to keep track of incidents closely and make sure everything I do goes through the issue tracker and version control.

This week, I learned that plans have changed a little, and I'm stuck with this co-worker for another month. This means I have a few more weeks of working together with this co-worker to go through, and I'd really like not to have to work in a way that creates alibis everywhere. I'd like to be able to work without having to look over my shoulder every moment, without him giving me the impression he's seeking revenge.

How do I best manage those last few weeks of working together with this co-worker, so that there will be no negative influence on the impression people have of me or of my career?

The only thing you can do is to do your work as normal, following all the proper procedures of your company. Limit your communications with this co-worker to only what is essential for this project and make sure that all of it is in writing. If you follow this path, the co-worker should not find any faults to expose.

Documentation is your friend.

In a scenario like this, the best thing you can do is clarify any potential point of uncertainty between you and this developer in writing ( email ). You won't have to do this for long obviously, but if you feel as though they may come after you in some subtle way, it is only prudent to attempt to protect your self.

Also, be sure to keep your manager in the loop on any interactions that have the potential to become a land mine. This way you can attempt to avoid having any additional departments becoming involved ( HR comes to mind here ).

I know this will be a bit of a documentation pain for you, but it is the best way to protect yourself.

Just follow your manager's advice: Make sure to log all your work through the ticketing software, do the work you're assigned, and that's it. If you are asked to do something, your response should be "send me a ticket". This should be your standard practice anyway, but it should really be your standard practice if you feel your work is under extra scrutiny and you need to make sure you can account for what you've done.

Be sure to discuss this with your manager, and ask how they want you to approach this. In a nonconfrontational way, ask why you're being made to work with the guy for the extra time.

By now, everyone who would be making that decision ought to know that there is friction between you, and it will interfere with your ability to get things done. The question, then, is why. It could be that there is an absolute need for additional work to get done, and this is the only way to do it. If that's the case... well, sometimes companies ask their workers to do unpleasant things. Buckle down, keep yourself covered, and tough it out.

It's possible, though, that they're building a case against this guy, or that they're trying to use this as a tool to push him into accepting what they need him to accept, or both. He's resistant to change, he uses poor coding practices, and a recent event just revealed some major issues with his behavior and/or attitude. As a result of that event, you're being called on to work with him longer. That at least suggests that things might be moving behind the scenes.

Admittedly, at that point your best answer is still to buckle down, keep yourself covered, and tough it out, but if you can understand the goals and expectations that management has for you, you'll likely be able to do it better, and may find it easier to get through.

On the flip side, it might be worthwhile to at least try to approach this guy from a place of compassion while you're here. He may have rage on the surface, but underneath I bet there's a lot of insecurity right now. If you can figure out where he's coming from enough to offer him some sympathy, it might help smooth things over. (Admittedly, it might also enrage him further. A lot of it depends on how well you do the "figure out where he's coming from" part.)

I'll put in a vote to try to clear the air by apologizing if only for the results if not the underlying dispute.

It sounds like you ended up causing your coworker a fairly large amount of grief over a relatively minor technical dispute. It sounds like you were technically correct. But you can still apologize for the results because it sounds like the impact is grossly disproportional to the underlying issue. You say that it hasn't damaged your career which implies that it has (at least potentially) damaged your coworker's career over something that's a pretty venial coding sin. From your coworker's perspective, it could realistically look like you were looking for a reason to throw them under the bus from the time you came over to the new team and you finally found it. That could well be causing them to expect that they need to look for something that you've done wrong if only to protect themselves.

It doesn't have to be terribly long. But I would take the coworker aside and say something like

"Hey coworker. I just wanted to clear the air with you. I'm sorry that I ended up bringing management down on you. That wasn't my intention. I should have found a better way to work through the work through our disagreement. I'm sorry."

Of course, even if you're totally sincere, there is no guarantee that the coworker is going to stop looking for reasons to return the favor and throw you under the bus. But ideally, you can convince him that you're not out to ruin his career over relatively minor dispute and de-escalate the situation.

You should still make sure that you are following every last element of your company's coding standards, development processes, etc. and you should make sure that you're documenting your interactions in case something comes back on you. But a solid apology may improve the atmosphere at work substantially.