If someone points out a specific action I did that can/should be improved upon (and especially if they can tell me why it was "bad" in the first place), I'm far more likely to accept that, attempt to learn from it, and move on. As in real life, I might still be heated in the moment, but I'll usually remember that when similar cues strike again.
But if moderation hints at something being wrong with my identity or just me fundamentally, then that points to something that _can't be changed_. If that's the case, I _know they are wrong_ and simply won't respect that they know how to moderate anything at all, because their judgment is objectively incorrect.
Practically at work, this has actually been a good policy you described when I think about bugs and code reviews.
> "@ar_lan broke `main` with this CLN. Reverting."
is a pretty sure-fire way to make me defend my change and believe you are wrong. My inclination, for better or worse, will be to dispute the accusation directly and clear my name (probably some irrational fear that creating a bug will go on a list of reasons to fire me).
But when I'm approached with:
> "Hey, @ar_lan. It looks like pipeline X failed this test after this CLN. We've automatically reverted the commit. Could you please take a second look and re-submit with a verification of the test passing?"
I'm almost never defensive about it, and I almost always go right ahead to reproducing the failure and working on the fix.
The first message conveys to me that I (personally) am the reason `main` is broken. The second conveys that it was my CLN that was problematic, but fixable.
Both messages are taken directly from my companies Slack (ommitting some minor details, of course), for reference.
If someone points out a specific action I did that can/should be improved upon (and especially if they can tell me why it was "bad" in the first place), I'm far more likely to accept that, attempt to learn from it, and move on. As in real life, I might still be heated in the moment, but I'll usually remember that when similar cues strike again.
But if moderation hints at something being wrong with my identity or just me fundamentally, then that points to something that _can't be changed_. If that's the case, I _know they are wrong_ and simply won't respect that they know how to moderate anything at all, because their judgment is objectively incorrect.
Practically at work, this has actually been a good policy you described when I think about bugs and code reviews.
> "@ar_lan broke `main` with this CLN. Reverting."
is a pretty sure-fire way to make me defend my change and believe you are wrong. My inclination, for better or worse, will be to dispute the accusation directly and clear my name (probably some irrational fear that creating a bug will go on a list of reasons to fire me).
But when I'm approached with:
> "Hey, @ar_lan. It looks like pipeline X failed this test after this CLN. We've automatically reverted the commit. Could you please take a second look and re-submit with a verification of the test passing?"
I'm almost never defensive about it, and I almost always go right ahead to reproducing the failure and working on the fix.
The first message conveys to me that I (personally) am the reason `main` is broken. The second conveys that it was my CLN that was problematic, but fixable.
Both messages are taken directly from my companies Slack (ommitting some minor details, of course), for reference.