What I learned about using Slack statuses when working remotely

bytebase.io

12 points·cborenstein··5 comments

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.

So, if I was involved in "deep work", then I wouldn't respond for a while. It never was an issue.

I do a middle-ground approach where I enable the macOS "red dot" for Slack on the dock, but disable the actual push notifications. This way I know immediately when I have a message, but a sequence of messages won't ping me over and over keeping me distracted.

I think this is similar with how the favicon displays the notification in a brower tab.

I read this years ago, https://words.motel.is/better-slacking-with-status-emoji-7a1... and installed their emojis on our work server, https://motel.is/slacking-better

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.

That and turn off slack notifications. You'll check it when you have time.

This reads like it was generated in some sort of Communist dystopia.

How about we not force people into a one size fits all API?

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.

If you want to code at night, then fine.

If you want to take DEEP BREAKS in the middle of the day, then fine.

If you and your team prefer to communicate intent and expectation via email, pigeon or certified letter, that’s fine as well.

Let’s measure success by results and trust people as adults to select their tools and manner in which they use those tools.

Reply on news.ycombinator.com