[one_off_comment]

The real story here is not about the code.

When it's your own personal project and you can be your own little tyrant, do whatever you want. Be as "clean" as you need to be. But this was at work, and Dan was being a bad coworker.

He snuck in a change in the middle of the night over a coworker's code. This code wasn't his responsibility. He didn't leave his thoughts on a PR where others could discuss it. He overwrote someone else's code without asking. There was no opportunity for discussion or collaboration. Dan's actions said he's right and his coworker is wrong. They said he doesn't trust his coworkers. They said he knows best. They said if you want something done right around here you have to do it yourself. Dan was not being a team player. This story is less about code and more about team dynamics.

I hope Dan knows this and he was just trying to sneak the message past people who don't take social cues as easily as others. I hope his boss didn't just tell him to revert his change. I hope his boss told him why.

EDIT: I just reread the article and I think Dan missed the point. This wasn't about the code, as I said. But Dan really does seem to think it's about the code.

[nacho_weekend]

Agreed, 100%. I would be beyond livid if a coworker did this to me if I were the original committer. OP does not realize the insane level of mistrust he just created with this action.