I'm still not sure how to deal with this, because everyone does it so I'm the weird one for finding it rude and disruptive to the conversation. The only thing I've come up with is to politely ask the people I interact with regularly and the people close to me to not check their phone during a conversation we're having.
(interestingly enough this usually sparks a conversation where they also express a dislike of constant interruption...)
If someone sends you a direct message they have the option to interrupt you if it's really important.
That's a minor thing but 'Zzz' really sends the wrong signal to the sender: if you are not available, then you are sleeping (i.e. unproductive).
Other chat systems offer the ability to attach a message to your AFK status, which can be pretty helpful for setting expectations about when you might be back. Last time I looked, Slack seemed kind-of resistant to doing anything like that.
Working remotely, is that a bad thing? If you are unavailable due to deep coding or a need for a nap does it matter?
https://get.slack.help/hc/en-us/articles/214908388-Do-Not-Di...
It may seem different on the surface, but it really is the exact same communication as you would have in person... you just need to ask. And much of the time, real-time responses aren't truly necessary... so you can just IM someone a question, and know they'll get back to you when they can.
I don't want my phone to notify me immediately every time a team chat message goes through. Direct hangouts messages have a higher "weight" and are useful sometimes, too, though.
Basically, this is just a cultural problem that needs to be worked out. Sort of like the (usually) understood idea that you shouldn't disturb a person wearing headphones and working.
No, it's absolutely not like that. The use case for "not dropping messages" is that you send a message and know they received it. You don't have to remember it manually, you don't have to introduce another chat system just to asynchronously remember to resend messages later. The other guy can respond at their convenience. Dropping messages would make the application a critical failure for any serious business uses. There are lots of features to mute notifications per room or for time durations.
Having multiple chat systems is ok, if they actually serve multiple purposes.
Years of socialization training stemming from childhood to gauge whether it's really worth interrupting people. I do enjoy the opportunity to do remote work, but even in the office, I'm finding an unstated expectation that I should always have a second pair of eyes on my slack notifications. It's not really consistent to praise the elusive "in the zone" state where developers get their most productive work done, and simultaneously expect that they should break what they're doing to bucket the importance of every little IM. The need to walk over to another person when you have something important to say, and use your human senses to determine whether this person should really be distracted for what you think is important at the moment puts the onus and effort of distraction on the asker where I think it best belongs.