Hacker News Reader

Comment by alberth | Hacker News Reader

Off topic: I see folks in the comments talk about async communication.

What I don’t understand about the async crowd is why then do you get mad when I email at 9pm at night, or I email on the weekend.

I’m not asking for an immediate reply, that’s the entire point of async (for you to reply on your own terms/time).

View on HN

Do they? At work we tend to encourage async communication, and one of the first things I heard when I started is that I might get emails / messages outside of working hours but there was no expectation that I'd read them, or reply if I did.

Async crowd is not mad at all! And in fact for a truly global & remote organization is impossible to schedule time for everyone. Just open your work email at times you work. Done.

I totally agree with you, but you can see even in this thread where people say things like "If a call to action exists the receiver will get mad at the 9pm email...What I don't know is the senders expectations of when the email should be checked"

I think this is using the term "asynchrouously" where others might use "off-line". When the meeting turns up a problem that isn't going to be resolved in a few words, you might prompt those involved/interested to organise a specific meeting rather than bore the rest.

However, "Can we take that off-line?" can also come to mean "Stop bringing problems!" :-)

Who gets mad at an email not viewed? If there is an expectation of responding immediately that breaks async people get mad. I have no ideas what emails came in over the weekend.. we will find out when the time is right

So you agree, disagree? I’m confused.

If a call to action exists the receiver will get mad at the 9pm email. I also know that an email not checked by the receiver they won't be mad. What I don't know is the senders expectations of when the email should be checked.

Reply on news.ycombinator.com