News for hackers. Stuff that matters.
Re:What the last few weeks have been like for the CEO of Slack by growse on Thursday March 26, 2020 @05:42AM (#22691931)
Email is a bad tool for discussion.

However, it can be a good tool for information dissemination. (There are better tools - I'd argue that sending information should be pull rather than push, but that's just my preference).

So yes, have a guy write something down for 30 minutes, get people to read it, and then have an actual conversation / chat about it.

Re:What the last few weeks have been like for the CEO of Slack by msla on Thursday March 26, 2020 @07:25AM (#22692442)
Email is a bad tool for discussion in that it lasts too long, and too many people can save copies; it's far better to have ephemeral and limited-distribution discussions, so if something obnoxious or actionable is said, nobody is opened up to legal actions.

The modern trend of people believing accusers is pushing against this wisdom, but it's still far better to not have evidence. That said, I'm sure Slack can be persuaded to destroy incriminating logs if the right pressure is applied. One of the benefits of people moving away from self-hosted solutions.

Re:What the last few weeks have been like for the CEO of Slack by closeparen on Sunday March 29, 2020 @04:03PM (#22722201)
Every enterprise-friendly messaging system offers configurable retention policies. Messages involving certain roles or keywords may need to be retained for years to comply with regulations, while others can be deleted after a few days to minimize risk.
Re:What the last few weeks have been like for the CEO of Slack by qznc on Thursday March 26, 2020 @05:59PM (#22698415)
I completely agree with you. By writing I was thinking about RFCs not emails.

Have a face-to-face discussion and have a shared written document. If I have to chose between the two, the I would favor the written document though.

Re:What the last few weeks have been like for the CEO of Slack by lukethomas on Thursday March 26, 2020 @06:35AM (#22692199)
When collaborating over ambiguous topics where the potential to be misunderstood is high, you need to use the "richest" communication channel possible. Body language, facial expression, and the fast feedback loop can help you quickly establish a sense of common ground.

On the other hand, status updates or sharing of metrics/information can easily be done asynchronously, because the potential to be misunderstood is low. It's also a more scalable approach and persists over time.

Re:What the last few weeks have been like for the CEO of Slack by jrandm on Thursday March 26, 2020 @08:27AM (#22692829)
> When collaborating over ambiguous topics where the potential to be misunderstood is high, you need to use the "richest" communication channel possible. Body language, facial expression

I would dispute that body language and facial expression are somehow always correctly interpreted or unambiguous, like most forms of communication.

Written word, or a series of characters in a string, as I think we in a technical forum with many programmers in particular can appreciate, can in fact remove quite a bit of ambiguity if everyone is careful about what they type.

Github has many examples of this in-progress.