Obviously, a low flow rating isn't a bad thing. Below that number, I gave a low flow rating. If the group's main channels consistently had over 30 messages, I gave them a high flow rating. I gave extremely high relevance ratings to groups that have a large amount of helpful subtopic channels with significant levels of activity.įlow ratings were based on an average of around 30 messages a day. Even some poor-quality groups had high relevance because, despite low levels of interaction, it was all on topic. I gave a rating of low relevance if more than 50 percent of the discussion looked unrelated to the topic of the group. My simple rating systemįor each of the groups, I submitted a request to join and took a look at the activity levels of the main channels. I'd like to share a semi-exhaustive, categorized list, along with my notes on the quality of each in terms of relevance, responsiveness, and activity/flow. While there are a lot of stinkers out there, I've also found many truly awesome Slack communities in the last couple of weeks. They look and operate a lot like the IRC topic channels we've had for years, but with more usability and a lower barrier to entry. He went off on a tangent at the start of his talk and said:Īs a result of Slack's burgeoning popularity and mainstream prominence (I've seen ads for Slack pasted on my local light rail), we've seen a bunch of developer topic-focused, public Slack groups popping up over the last few years.
At a software architecture conference last year, one of the speakers, a performance engineer, was talking about great application UX.
0 kommentar(er)
