[r00fus]

So the boss throws out the article on a slack channel without any context? Sounds to me like if you want +1's that's what you do.

If you want reasoned discussion, there should be an ask from the boss on the channel-toss even if it is a @TheRealmccoy call-out on the posting.

[TheRealmccoy]

Again, the React v/s Respond conundrum.

At hindsight, if you look at a Slack channel, so much information would be found redundant.

It is there just because it is so easy to put out there, because of the intrinsic nature of the medium, and it is so because, most of it is reaction.

Like, oh this is nice, let's put it out on Slack.

While writing an email,when the communication is being initiated, there is sufficient pause built in the system, to let one ponder, is this really worth it?

Email is not fool proof either of this syndrome, but far better.

[r00fus]

What makes email inherently better for your React/Respond dichotomy?

What prevents redundancy is searchability. Most email clients are great for that, but Slack's searchability is inherently better than email - if you're not part of a channel (because you weren't on the team at that point), posts can be searched once you do gain access to the channel.

Emails between other team-members excluding you cannot since you will never have access to them.

There are so many times I just link back to a previous answer on the topic and just h/t the original poster. Takes a moment, but is far more definitive.