Also Teams:
this post was submitted on 14 May 2025
197 points (99.0% liked)
memes
14723 readers
3214 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 2 years ago
MODERATORS
I love teams.
ever since my job has dedicated Teams as the only way to communicate I haven't been harassed as much by dumb fucks.
either their app is broken, or mine is "broken". I probably talk to 3-5 people a day vs 20-30 a day via Slack.
πΆI'm lovin itπΆ
Teams is one of the worst applications I ever had to use
Teams is the most reliably unreliable piece of software.
Serious question for anyone who knows about this sort of thing, new teams is an electron app right? Which from my understanding means it's basically just Chrome that only loads a single page? So how the fuck does it break so often!?
I work in the industry (not MSFT) on cloud reliability so I have insight.
- The cloud itself is not as stable as some people may think. Standard is 99.9 % uptime. Which sounds great, but if your DB is 99.9 % and your compute is 99.9% and your storage is 99.9 % and your network and so on and any one of those going out breaks your application, then you don't have 99.9 % but
(99.9 %)^nwhich is a lot less impressive. You can make things fault-tolerant through redundancy but that comes with great complexity which can cause outages of its own. - Apps like teams, like most B2B bullshit, provide added value by bundling together as much shit as possible. Chat, calls, calendar, spreadsheets, you name it. So now any one of those features going out individually can impact the whole app.
- Every one of those features in the bundle is managed by a different team, possibly in a different country and coming from a different company acquisition. So now you have to glue unrelated tech stacks together which is super expensive.
- The way you bundle things together in a SPA in a corporate environment with finite resources is by basically bundling together a bunch of iframes. Ever notice that the calendar tab on teams sometimes tells you to refresh your page to get new credentials? That's why, this fucking thing bundles its own authentication lib and barely talks to MS Teams so it can't properly refresh its tokens! If you like having one product's technical debt, now think about having 20 products' technical debt all conveniently forced to interact together in one web page!
Honestly I'm impressed by how well teams works with the very severe constraints they clearly have. Shit's got more moving parts than Ryanair's entire fleet and it only breaks once in a while.
Because its backend is SharePoint.
because it's a cobbled-together piece of intangible complicated software, that's gone through two major iterations for no good reason.
I only ise teams for meetings on occasion for one external client, but it breaks this much when you open it up in the browser as well.
Self sabotage