3 ms·
Email. I work at a software development shop and most of our internal Email-like communication happens face-to-face or via phone. "Will you be available for a
by virtualized 9y ago
Email.
I work at a software development shop and most of our internal Email-like communication happens face-to-face or via phone.
"Will you be available for a meeting two weeks from now?"
"I just wanted to tell you that I checked in my code."
"Please answer my trivially Google-able programming question right now."
"Tell person X that I want to talk to them later."
"The boss just told me [important news that concerns several people who are not at work today]."
I have to assume that most of the world works like that and Open Source communities are the great exception to this rule.
- adrianmsmith 9y agoI have been thinking about this recently and come to the following conclusion: - If you receive a call, it breaks your flow, which is bad. - If you send an email, it breaks your flow, which is bad. (As you have to wait for an answer, and do something else in the meantime.) So if you have a question, the optimal strategy (for you) is to make a call. But if someone else has a question, the optimal strategy (for you) is they email you. There's even a further level, which is that if someone else has a question, it's optimal (for you) that they email you, and you call them to give your answer, and discuss it until it's done. So if it's up to you (and you're thinking only about your own productivity above all else) then tell people to email you when they need something, but call them when you need something.