This kind of sadly has been the most effective. Previously when I did this he'd re-litigate this over slack and in meetings again and again, trying to prove this was a bad decision. He's stopped doing that after my manager told him to knock it off.
I say "sadly" since this is basically pulling rank, which I don't want to have to do. But I don't think he'll leave -- he seems really entrenched in, having worked on the team for a lot longer, and seeming to enjoy it anyway.
It's also hard to ignore in team meetings without things being tense and awkward. I can easily come across as "the bad guy". And the last lead was a lot more willing to lay down the law like that -- the team completely fell apart and everyone tried to get each other fired, and it just took a single quarter for that lead to leave.
It's all risky and high-stakes, since I do really value my position and enjoy it (except for this) -- I can easily turn into the bad guy.
Can't. As I said, they don't have any on-phone support anymore. I tried for a couple days but it's not possible to reach a human anymore. No keywords like 'representative' work now. The try to offer automated support or redirect you to webpages, but that's it.
It's when your director goes and tells you not to tell anyone but to report to another building to another team for a month or three, and help them with whatever they ask, because you have a very specific set of skills. (In this case, setting up VPN backend infra.)
With commit messages you miss the point. It’s more like the final test of the commit. If you can’t formulate easily what you did and why, then you need to rethink your changes.
Never give up against him. Push through your ways every single time.
Sooner or later he’ll get the point and he’ll leave.
reply