Re:Programmers, teach non-geeks the true cost of interruptio...
by MattGaiser on Friday July 09, 2021 @05:08PM
(#27788528)
At least on the teams I have been on, we didn't physically interrupt people. We sent Slack and Teams messages for all of that stuff about merges and staging.
[ Parent
| on HN ]
Re:Programmers, teach non-geeks the true cost of interruptio...
by snarf21 on Friday July 09, 2021 @08:45PM
(#27790100)
Fair, but I think Slack/Teams are just as disruptive as physical interruptions, at least to me.
Re:Programmers, teach non-geeks the true cost of interruptio...
by lolinder on Saturday July 10, 2021 @12:09AM
(#27791040)
How disruptive depends on company culture. If the expectation is to respond immediately, it's no different than a physical interruption. On the other hand, I leave Slack notifications off and only use it through the browser. Usually, I only notice the tiny glowing favicon once I'm largely out of the zone anyway.
Re:Programmers, teach non-geeks the true cost of interruptio...
by cratermoon on Saturday July 10, 2021 @12:09AM
(#27791037)
There's definitely an issue with notifications in things like Slack/Discord/Teams, but it's a symptom of a larger problem software where everything is competing for attention. Social media apps do it because it's part of their business model and built in to the addictive-by-design need to get eyes on ads.
Chat systems aren't (yet?) dependent on ad revenue, so they don't need to copy the behavior of social media, but, possibly because they use the same operating-system level notification APIs, that's how they act.
Re:Programmers, teach non-geeks the true cost of interruptio...
by varjag on Saturday July 10, 2021 @07:58AM
(#27792771)
This weird preference on here for Slack interruptions is just another manifestation of generational call vs text divide. It's more about cultural context and personal anxiety than real disruptive effect.