Story of the most annoying coworker I've ever worked with at a past company. I will not name names or disclose any information regarding the individual or company. The reason why I'm sharing this is to give an example of how you *shouldn't* act in a collaborative environment. No hard feelings. New hire joins the dev team. Everyone is optimistic and happy to welcome them. The first thing I do at the start of my work day is taking the time to review my coworkers' PRs to keep everything moving quickly. I see that the new hire opened their first Pull Request. I go in and review it. It's huge. ~1200 line diff. Code patterns don't really match the codebase. Commits co-authored by claude. That's expected from a new hire. I leave an extensive and detailed review and continue working on other stuff. Later the new hire responds to my review. Zero changes addressed. A barrage of very verbose and defensive comments. The comments are verbose enough to suspect the use of AI. One comment mentioned "a 1:1 call" For context, some other non-technical coworkers at the time were using claude to write small PRs, and claude was responding to my review comments on their behalf. I send them a DM asking whether they made the comment or if claude commented on their behalf, citing the 1:1 call mention. A response comes back: "Well there's your answer" I pound my fist on my desk. The nerve. You just joined the team. And this is how you talk to someone who's been here for so long? I set aside my feelings and take up the 1:1 call. Turns out the new hire came from a company that required him to ship a large volume of features in a very small time window, running 4 agents in parallel. I tell them they can slow down a little and how do things a little slower around here. I walk them through some of the code patterns. We reach a point of understanding. Or so I thought. Fast forward a few days. More PRs come in from this person. Every single code change is drastically different than the existing patterns in the codebase. It's bad enough that even an LLM wouldn't introduce code that was this out of touch. Every time I offered feedback, they walked through a mile of glass to defend it, then proceeded to leave the PR in the dust without addressing anything. I just felt so disrespected. I took the time to read the code that this person probably merely *glanced at* because I care about the software I'm building. In return, I get shoved away. And they continue like nothing ever happened. I talk with a different coworker who I closely work with. He reports feeling the exact same way. We talked to the lead engineer about the new hire. The lead engineer was approving and merging these PRs on the basis that they worked. To be fair, he was onboarding the new guy. Over the next few days, I try to put up with it. I try to reason and resolve the situation. More back-and-forth DMs. And then I snapped. To the coworker that I closely worked with and discussed the new hire with, I send "If they [the new hire] won't bend, I'll break 'em". On a review that was, once again, not adhering to any existing code patterns, I commented something like "You're not addressing ANY of the feedback I'm leaving ... I already have my LLMs to babysit. I don't want to have to do that for you" (Please don't do this. I am not trying to justify my actions here. I was definitely in the wrong for this) The lead engineer saw my comment and gave me a stern talking to. It ended up with the entire dev team getting together and deciding what was reasonable grounds to block a PR from being merged. We created a code review principles document that said stuff like "If the PR does what it says *correctly*, it's mergable" "Don't make the review about the person, make it about the code" "To enforce a code pattern, it must be explicitly mentioned" etc Time went on. The PR review process with this person stayed the same. I'd absolutely had it at this point. I messaged the lead engineer about how I felt. "" I just feel so disrespected after taking the time to give a thorough review, only to have it shoved away I don't want to make it about the person. I've tried. It's not working. If every file in a directory is in kebab-case, does that give someone the green light to add a new one in camelCase just because it's not explicitly mentioned as a code pattern? It's like 'Do you have the courtesy to put away the shopping cart? Do you have the courtesy to put the weights back? Do you have the courtesy to at least tell your LLM to _follow the existing code patterns_? "" It ended with the lead engineer offering to review PRs from the new hire himself.