> Teams is extremely well integrated with the rest of the Microsoft suite. Erm. Not sure someone who's used it would say that :-)
He's not wrong, it's well integrated, but they're all shit just easily connected. E.g, SharePoint is absolutely awful.
The Problem with Slack at Scale
61–70 of 107 posts
Re: The Problem with Slack at Scale
#62It’s wild that Google, despite being the leader in startup email/business software and literally giving their Slack competitor to everyone for free as part of their Google Business subscription, STILL has such low mindshare in this space that it didn’t even merit a mention in the blog post. (Full disclosure: my company used Google Chat, and I find the integration ecosystem so pitiful that I’m constantly thinking abou…
The original Google Chat (with the little Windows client that sat in your taskbar) was surpringly good.
And then, of course they killed it and made it a web UI thing and made it majorly worse at the same time
Re: The Problem with Slack at Scale
#63> Slack Alternatives > 2. Slack clone but with Feature X. Feature X is usually something like task management, project management, notes etc. Examples of these apps are Chanty, Rock.so, Flock, Ryver, Twist (there are many more). > The problem with the apps in the second category is that they end up competing with two existing tools. I use 4 written communication tools: 1. Slack for (a) async & sync team chat (b) asyn…
For the whiteboarding solution at work we use Miro. Extremely happy with it
Re: The Problem with Slack at Scale
#64I've long held the opinion the best chat app is no chat app, i.e. delegate everything to your favorite issue tracker and other forms of knowledge keeping (e.g. Git commits, design documents). Let everything be either fully 'literate' (for lack of a better term: abundant context, complete paragraphs and argumentation, hyperlinking), or fully sync and human (meetings), with no in between other than email, used thinly.…
I work for a company distributed across the world with ~200 users in our 'watercooler' channel. I can't think of a better alternative to Slack that would enable everyone to stay in touch and feel part of a community. Email, forums, or — god forbid — enormous video chats would be overkill.
Re: The Problem with Slack at Scale
#65I'm actually really interesting in this. What are the top 3 things you could change in slack / teams that would make you switch. I'll go first:
* Notifications settings are annoying I'm either swamped with notifications or miss them. I want to be able to switch of notifications for short periods
* I want to group discussions about certain things. I.e. if we are discussing a JIRA issue I can select the message and group them into something that I can attach to the issue we are discussing
* Too many private chats - I'd like to ban private chats as I find there's some great info in these which are often not shared to the group
Re: The Problem with Slack at Scale
#66I've long held the opinion the best chat app is no chat app, i.e. delegate everything to your favorite issue tracker and other forms of knowledge keeping (e.g. Git commits, design documents). Let everything be either fully 'literate' (for lack of a better term: abundant context, complete paragraphs and argumentation, hyperlinking), or fully sync and human (meetings), with no in between other than email, used thinly.…
> It's a model that has worked well for OSS - many projects do just fine with Github alone, sustainably, for years. What's the biggest OSS project you know of with no IRC, Discord, Slack or other chat presence?
The question is loaded because while a OSS project might have chat "presence", it doesn't mean at all that its organisation revolves around said chat medium.
Chat is more often a support channel.
When you keep in mind the scarcity and distribution of OSS maintainers, the need for asynchony will be evident.
(If you want an answer: multiple 1k+ stars projects I'm a maintainer of)
Re: The Problem with Slack at Scale
#67I cant believe I read Slack and fast in one sentence.
We use mattermost and its mostly OK to the point i'm willing to use it which cannot be said about Slack. Forcing me to have Slack open all the time was reason I left a job. It was unbearable.
Re: The Problem with Slack at Scale
#68We adopted Slack and I hate it but use daily. What I find so frustrating with Slack is that it's 1. Super terrible at threading. Threads are clearly discouraged and don't nest. This appears to be by design, but even Usenet handled threading better. 2. Slack is an information wastebasket - at least in my experience it's really hard to find information once there's a significant traffic in a deployment. 3. Too Much Not…
I used to hate Slack, then I got involved with some projects that require Teams,....
It's baffling the degree to which Teams doesn't work on a purely technical basis, before UI and UX even come into play.
Half an hour ago I accepted an invitation to join a Team. Logged into MS in the browser, checked remember me, and then... a naked JSON response. It had a field "result", value "Success". Good! What now? Nothing else happened.
I firmly believe Teams is only usable if you're a Microsoft shop (don't even think about Firefox and friends) and is managed by a central IT (I somehow have two MS accounts under the same [work] email and no idea which is which). Don't get me started on being on Teams as an external employee.
Things like Slack just work much more and are much less surprising in their behaviour.
Re: The Problem with Slack at Scale
#69I cant believe I read Slack and fast in one sentence. We use mattermost and its mostly OK to the point i'm willing to use it which cannot be said about Slack. Forcing me to have Slack open all the time was reason I left a job. It was unbearable.
It's surprising to read that. No one at work hates it so much, afaik. I wonder what's different about our channel lineup, usage habits, or anything else that is such a contrast to your experience.
Re: The Problem with Slack at Scale
#70> Slack Alternatives > 2. Slack clone but with Feature X. Feature X is usually something like task management, project management, notes etc. Examples of these apps are Chanty, Rock.so, Flock, Ryver, Twist (there are many more). > The problem with the apps in the second category is that they end up competing with two existing tools. I use 4 written communication tools: 1. Slack for (a) async & sync team chat (b) asyn…
I'm always curious about how different teams have "solved" whiteboarding with distributed teams, as they are normally then not whiteboarding but using a collaborative diagramming tool which is much too restrictive. The closest I've found is making sure everyone has a decent sized tablet and using Google Jam.
Miro works well for this, you don't need to use it as a diagramming tool.
AWW was awesome at this, free-form drawing was the default, you'd just doodle whatever you wanted, no structure required.