They objectively take longer. And honestly, nuance is lost in text. Especially if you rush it and dont use grammar, use abbreviations slang without context.
Text is good when you need to convey things that take a long time to find. In IT that means, ip-addresses, fqdn, configs etc. But if i need a yes or no answer, i wont be sending an email or even a dm. People have shit to do and they might be waiting for me/the response to get back to their own thing.
What nuance. Thanks to the time I can spend writing a message, I can commit to adding the details in readable format, and this data stays for reference. Whether it’s instruction, some info or a question.
During call, I am scrambling to answer ASAP - like a lot of folk I know, and seemingly a lot of commenters here - so you get partial, jumbled up answer.
Calls are okay when asking about preference - something you can answer from the get go - if you want some information, use message.
They objectively take longer. And honestly, nuance is lost in text. Especially if you rush it and dont use grammar, use abbreviations slang without context.
Text is good when you need to convey things that take a long time to find. In IT that means, ip-addresses, fqdn, configs etc. But if i need a yes or no answer, i wont be sending an email or even a dm. People have shit to do and they might be waiting for me/the response to get back to their own thing.
What nuance. Thanks to the time I can spend writing a message, I can commit to adding the details in readable format, and this data stays for reference. Whether it’s instruction, some info or a question.
During call, I am scrambling to answer ASAP - like a lot of folk I know, and seemingly a lot of commenters here - so you get partial, jumbled up answer.
Calls are okay when asking about preference - something you can answer from the get go - if you want some information, use message.
So exactly what i said?
With nuance, im talking of inflections from speech. Which you can’t get from text.