Layoffs and having to use teams? Talk about a morale hit
Those MS solutions are just worse than the competition, and getting frustrated at your bugged technology because the parent company decides it can save some money is just trading employee satisfaction for dollars.
Honestly I wouldn't be surprised if this is 'our' fault, as I'm sure someone will point out. But in the years of using Gmail at my last employer, it just worked.
Maybe it's a setting an admin disabled, if it's literally every email chain.
It doesn't even save money - the cost is just shifted from subscription expenses to lower dev team productivity. Management can't measure the latter as easily as the former, and arguing against switching is a much more complex argument to understand than "this number is bigger than that one".
There's a very appropriate classic quote for that sort of situation: "Not everything that counts can be counted, and not everything that can be counted, counts."
I click on email, it takes few seconds to render that few lines of text. I click on one below, same 3-5 seconds. Emails I read few mins ago. Click on Calendar, again 3-5 seconds for switch. But then teams is same, effin' chat and nothing more, but also has proper UI bugs visible all the time, ie read stuff still has notifications. Having web call in it with screen share kills CPU for good. Our hardware is not the best currently but pretty recent and definitely things should be smooth.
What is it, implemented in javascript?
One aspect of where I work (large old tech company) is that we value those that can adapt. You aren't judged as much by your skill set as you are by how you use your skills or work with the skills others have. Sure, there are limits and this doesn't mean you become the metaphorical frog in the slowly heating pot of water.
There's certainly folks who enjoy the challenge or adaptation, but it does show a certain attitude towards the work and workers if your management doesn't think you need good tools to do the job well.
I'd stick around in a bad job if I thought I couldn't get something better, but it definitely means I'm looking to leave when things recover.
4 years was the standard for a long time, these days many companies are moving to 5 or even 6 years for laptops.
Hell right now I have employees at 4 years that refuse to change out their laptops because they have no problems with them and want to keep them longer
It was barely usable in the end, but I didn't want to be locked into years of crappy keyboard et al when the improvement was Just Around The Corner™.
Performance translates into more productivity for employees spending most of their time in front of one.
Even JIRA and Confluence are way faster on my 2021 M1 compared to my 2019 MBP due to the javascript runtime being much more performant. Admittedly a bit of a cherry picked example, but still.
It's like most people forgot that in the early days there was a phone and it worked just perfect. Everyone was reachable through it. Now I need to check multiple channels for the same thing.
Which is why outages usually match Azure outages.
Our AWS spending is outrageous tbh
-The phone dial in option doesn’t exist when you call someone through teams. Only on scheduled meetings. My laptop has audio issues so I have to awkwardly decline calls and send a meeting invite to whoever was trying to reach me.
-Sharing a file in the chat for a meeting puts it into some incomprehensible internal sharepoint structure that is tied to that specific meeting instance and is difficult to ever find again.
-Switching from speaker to Bluetooth headphones on my phone regularly crashes or freezes the app.
-Worst search feature I’ve ever seen for a messaging app. If I manage to find the right keyword it will take me directly to the message, but not show the rest of the thread the message was in. I have to use the date and scroll back up until I hit in in the regular view.
And prevents you reusing file names. If you uploaded "image.png" or "notes.txt" to a "Team" (room) once, it will make it awkward if someone tries to upload another file with the same name in the future.
Terrible UX.
It's been a while, so I can't remember exactly where it put them. But the directory structure had the room name in it. As a user I didn't get a choice where they went.
Only app that has this issue with bluetooth audio. WTF.
But it also feels more cumbersome. With unlimited money I'd probably use slack and zoom instead. There are just so many little confusions, weird stuff where a team is has a sharepoint but it's not exactly a sharepoint, and it's never obvious where stuff is, and it defaults to opening office documents in some crippled teams-specific reader instead of their usual application. I know there's logic underneath it all, it just feels more clunky and enterprisy then the relatively seamless experience of other software.
(Edit having just seen the parallel post to mine: the default email notifications are obscene. Getting an email because I didn't look at a message after one hour is super annoying, and is borderline "bullying" in a corporate environment. It's possible to turn it off, but the defaults suck)
Ah. There you go.
It's even worse on non Apple silicon Macs. It doesn't seem to care that you have an I7.
Zoom call quality is far superior and the client is less of a pig (if you don't use Team's web version).
Now, for text conversations? Teams is borderline unusable. Given the option I'd rather use IRC (Team search is horrible anyway). If you are used to Slack, it's horrible.
Just about the most important thing a business chat app could do, right?
Another thing is that I have to use Intune to use Teams on my phone. Now, I know that's a choice the IT department made, and my employer is to blame here. But at least Zoom and Slack don't even give them the option to mandate bundling literal spyware.
I also dislike the concept of having teams and chats in separate places, with the two having a completely different flow of usage.
It will often silently log you out. Then, you're sending messages going into the ether, assuming you are communicating. Except you are not. You have a silent morning w/o any firedrills, until at 11am, you discover you're silently logged out and there was a small popup screen that is hidden asking you to log in again.
You are on a Teams video call, and you cant seem to create another window on your phone to look at chats. Makes no sense.
The real estate required for Teams is so huge. Slack is incredibly space-efficient but Teams is not. Much like MSN Messenger, a lot of the space seems like deadspace.
Cant keep a great group chat by turning it into a channel.
Writing bots for it is also painful.
Maybe it wasn't specifically Teams, but screen sharing used to be a massive performance hit (MBP around the year 2019). I remember giving a demo, and a response from a keycloak container I was running locally timed out.
It made it very awkward to copy and paste multiple messages in a chat.
For a primary communication channel, teams is terrible.
As long as I can use an IRC inspired tool (slack, discord, irc) to chat, I'll tolerate teams as a virtual conference room.
To be honest, it's not awful if you're only using it for that.
a Lattician, a Flexporter, a Scalien, a Relativian, a Plaid, a Swyftxer, an Elastician, a Krakenite, a Dragon, an Asana, a Wistian, a Nuron, a Bird, a Twilion, a Pitcher, an Olivian, a Snyker, a Panda, an Astronaut, a Superhuman, a VTEXer, a Klarnaut, a Lacer, a Mozillian, a Paddler, an Oyster, a SoundHounder, a Vimean, a Zoopligan, a Motive, a Stasher, a Plerker, a Lokaliser, a Courserian, a Udacian, a Racker, a Gitpodder, a Dutonian, a Googler, a HubSpotter, a Workmate, a Splunker, a Zoomie, an eBayer, and a Hubber
A Lattician, a Flexporter, ..., an eBayer and a Hubber walk into a bar. But in the end, they can't afford getting anything to drink since they've been laid off.