It would also be nice if you could clearly denote who a thread needs attention from. Eg in a #design channel it would be nice to create a thread like "Increasing accessibility on the checkout page" and to then mark the people you think need to see the thread.
This is exactly how we use threads. With @ mentions. It is somehow ok for us without suggesting urgency. We're just trying to be really careful with each other's attention.
I suppose if everyone agreed that this was what we were doing, and everyone always used threads, it could work well. I'd be curious how this compares to one of the other tools out there (eg Twist)
My friend worked in Doist on Twist back in the day and he hooked me up on the early beta.
I think Twist is like Basecamp. It's good for planning and long conversations, but it sucks when you need to discuss something quickly because you end up in a direct messages conversation. I ended up using Trello + Slack, and Google Docs for planning.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is exactly how we use threads. With @ mentions. It is somehow ok for us without suggesting urgency. We're just trying to be really careful with each other's attention.
I suppose if everyone agreed that this was what we were doing, and everyone always used threads, it could work well. I'd be curious how this compares to one of the other tools out there (eg Twist)
My friend worked in Doist on Twist back in the day and he hooked me up on the early beta.
I think Twist is like Basecamp. It's good for planning and long conversations, but it sucks when you need to discuss something quickly because you end up in a direct messages conversation. I ended up using Trello + Slack, and Google Docs for planning.