When giving feedback during code review, I try to check my assumptions by asking questions regarding the intent of the code, whether we can prioritize follow-up work at a later time, and, most of all, the sanity of the test suite. When working with more junior developers, I prefer to ask them questions instead of giving them advice. Being self-taught in Ruby, I truly believe There's More Than One Way of Doing the Same Thing.
I adapt to my environment. I bring my sense of humor when submitting PRs, but I hold it back when commenting on someone else's. If I have a concern with how an interaction occurred, I'll follow-up with the people involved directly, and I expect the same in return. We spend the majority of our lives in our workspaces, so we cannot simply check our baggage at the door; if I am frustrated with how someone engages, my first question is how I can alter my expectations of them and not how they can change to accommodate me.
I historically have a nasty habit of over committing and taking on every opportunity to help at my own expense; making sure I haven't set more than two Slack channels to always notify is part of my mental health checklist. Instead of trying to prove myself by jumping to help without consideration for my current obligations, I will seek to encourage "volunteer delegation" by prompting any someone to take direct ownership or to take ownership of prioritizing delegation.