Hacker News Reader

Comment by beberlei | Hacker News Reader

Hey, these all sound like very good hints on how to use Slack, especially the consensus on decision making. Maybe we have used Slack wrong, but especially the context was important for me and Slack threads are hard to enforce, you can "break out of the jail" easily, often by mistake.

View on HN

> Slack threads are hard to enforce, you can "break out of the jail" easily, often by mistake.

In particular, image uploads (and possibly other attachments?) are always posted to the main channel, even if the message they were attached to was in a thread. Trying to conduct an image-heavy discussion -- like a discussion about a graphical design -- in a thread will just mean the main chat gets interrupted by a bunch of out-of-context images.

This was improved over recent months by Slack.

This resonates with me more easily than the tone of the OP. Slack is a very good tool. For some reason, bashing it is all the rage now, but most of the criticism is misplaced and unsubstantial. FWIW, I use Slack even though I work alone, just because the integration with various 3rd parties makes it a fantastic notifications hub (which I can silence/relay/amplify at will).

Hah, but I am the op :-) I didn't want it to come out negative. I don't think my critique is unsubstantial though. Essentially we switched Slack with Basecamp, which also offers a chat part, so you can replicate the same behavior, but it also offers other means to communicate. Slack in this case was just the chat tool we used, I think the problem is with chat as primary company communication, independent of vendor.

Yeah, I wish you could migrate messages to a thread retroactively.

Reply on news.ycombinator.com