There's a deep fear that software engineering can't be reduced to correct and incorrect like a math formula or the scientific method. This leads to rigidity, and I'm glad there are articles like this calling it out.
Tragedy of the commons. People will prioritize selfish, short-term gains by taking from a finite pool of resources at the expense of long-term sustainability for everyone.
I use Teams but I usually just leave on read as a signal to get to it later when I have time. I have notifs muted. But I'm also not pinged so often that I need tactics like this article. Good stuff.
It's "unread", not "on read" by the way. I would not normally mention this type of correction, but I've noticed it more frequently and the two phrases are antonyms, unlike the common "lose"/ "loose" mistake.
