What I learned about using Slack statuses when working remotely

when I used Slack at work, I never bothered enabling desktop notifications, so even if someone messaged me, I would only see it when I decided it was time to check the Slack tab in my browser.<p>So, if I was involved in &quot;deep work&quot;, then I wouldn&#x27;t respond for a while. It never was an issue.

I read this years ago, <a href="https:&#x2F;&#x2F;words.motel.is&#x2F;better-slacking-with-status-emoji-7a172acef2a4" rel="nofollow">https:&#x2F;&#x2F;words.motel.is&#x2F;better-slacking-with-status-emoji-7a1...</a> and installed their emojis on our work server, <a href="https:&#x2F;&#x2F;motel.is&#x2F;slacking-better" rel="nofollow">https:&#x2F;&#x2F;motel.is&#x2F;slacking-better</a><p>You share the link. If they see it good and if not, when you hover emojis it shows the name. When someone sees `:working-head_down_no_interruptions:` they get it.<p>That and turn off slack notifications. You&#x27;ll check it when you have time.

This reads like it was generated in some sort of Communist dystopia.<p>How about we not force people into a one size fits all API?<p>Let’s trust grown-ups to be grown-ups and communicate the things that are important to them in the way that they deem important.<p>If you want to code at night, then fine.<p>If you want to take DEEP BREAKS in the middle of the day, then fine.<p>If you and your team prefer to communicate intent and expectation via email, pigeon or certified letter, that’s fine as well.<p>Let’s measure success by results and trust people as adults to select their tools and manner in which they use those tools.