I concur with Peter Frank's initial point -- while written communication is bound to be the primary form of interaction on a remote team, some conversations are really better had voice, or even better, voice-and-video.
The problem is really very simple when you think about it: no matter what emoji or formatting choices you try to incorporate to influence how your text is perceived, in the end, the reader is not going to "hear" it in the voice you "spoke" it; they're going to hear it in a voice in their head, with their own biases and their own emotions, not the ones you intended.
If software discussions were entirely emotionless interchanges, this would not be a problem; but that's not reality. Reality is that we are, on the whole, actually pretty emotional about our own work, and often pretty passionate about what constitutes "good" design, "good" code, etc.
For a while, I managed a very widely distributed team -- we had people in Bosnia, Serbia, Argentina, California, and Minnesota. Most of our conversations were had in HipChat, or in GitHub PR discussions; but every now and then, text simply wasn't adequate to the task. A conversation, real-time, voice and if possible video, was necessary to really clearly convey nuances.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I concur with Peter Frank's initial point -- while written communication is bound to be the primary form of interaction on a remote team, some conversations are really better had voice, or even better, voice-and-video.
The problem is really very simple when you think about it: no matter what emoji or formatting choices you try to incorporate to influence how your text is perceived, in the end, the reader is not going to "hear" it in the voice you "spoke" it; they're going to hear it in a voice in their head, with their own biases and their own emotions, not the ones you intended.
If software discussions were entirely emotionless interchanges, this would not be a problem; but that's not reality. Reality is that we are, on the whole, actually pretty emotional about our own work, and often pretty passionate about what constitutes "good" design, "good" code, etc.
For a while, I managed a very widely distributed team -- we had people in Bosnia, Serbia, Argentina, California, and Minnesota. Most of our conversations were had in HipChat, or in GitHub PR discussions; but every now and then, text simply wasn't adequate to the task. A conversation, real-time, voice and if possible video, was necessary to really clearly convey nuances.