Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub staff are required to use Teams by Sep 1, 2023

twitter.com

Post reply on HN
Print view View original

671–680 of 725 posts

Re: GitHub staff are required to use Teams by Sep 1, 2023

#671

Post by gabrielgio »

jdlshore wrote: post #550
lpbonenfant wrote: post #398

I don't understand most of the negative comments in this thread along the lines of "if my company would require I use Teams I'd quite on the spot". Really? an IM client is what's going to make you quit? I always thought it was amusing that old developers were super anal about vim vs emacs and saw it as a tongue in cheek but now I realize most of those people are really serious and take these things quite emotionally.…

It's a tool that people use day-in, day-out for all their communication with colleagues. If it's unpleasant to use, the majority of your work becomes a constant reminder of that unpleasantness.

Exactly, if my chat, my email, my git server, etc. are unpleasant it will make my workflow unpleasant and so will my job as whole. I have changed jobs due tooling being a pain before.

I'd never quit on the spot though, I'd silently search for another job.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#672

Post by AnonymousPlanet »

dbancajas wrote: post #470
ygjb wrote: post #209

Earlier quoted context omitted.

I will be blunt. Teams is an awful user experience; I have been using online collaboration tools since the BBS days, and while I appreciate and understand why and what they are trying to build, it is bad software. Every single experience I have had as a teams user in professional settings, interacting with communities, and being required to use it for interactions with my childrens schools since the 2020 shutdowns ha…

What is the specific complaint against it? Better yet can you come up with tools that you use instead of Teams? Is it xoom? Slack? Discord? MS is not my favorite company but my MS Teams experience has been relatively smooth.

We use TeamViewer for online meetings. Lets you share your screen. It's also used for support on customer sites. Works very reliably. We use Teams or WebEx only when interacting with customers and they demand those applications.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#673

Post by bartvk »

azalemeth wrote: post #551
generalk wrote: post #421

Regardless of what you think of Teams -- I myself have had nothing but poor experiences over 2.5 years of using it daily -- it's telling that Microsoft has to require folks to use Teams. I'm sure this is just Microsoft unifying everyone on the same comms platform, but seriously, I don't know anyone who chooses Teams. I know non-tech folks who chose Outlook 365 because of familiarity and then end up on Teams because i…

If nothing else, Teams is horrendously inconsistent and one might naïvely think that MS would want to dogfood it better, with good statistics. This HN article now has nearly 600 comments of people – mostly – griping about Teams. A large number of them are replied to with people saying "Oh, it's never done that for me!" or, alternatively, "Teams never works fully, but at least X works" being replied to by "X has liter…

Exactly, thank you so much for putting the experience into words. The random errors are just so... astoundingly random.

I've had problems with a headset on USB-C (Sennheiser EPOS). Teams would connect once, and then never again. Another time it would stop responding to any click. Then it would reload whenever changing team/channel. And then it would no longer show any notifications.

I haven't seen an app with that amount of apparently completely random errors, often not reproducible either. It's like a Bethesda game.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#674

Post by wkat4242 »

vel0city wrote: post #589
wkat4242 wrote: post #586

Earlier quoted context omitted.

> Now, that document isn't just in that chat, its also in the OneDrive/Sharepoint and in the history of recently opened documents in something like Excel or Word or Powerpoint. That for me is a huge drawback because it's constantly cluttering up a huge mess of different document versions in SharePoint and teams itself. Try to search for the right one a few weeks later. Good luck :)

I don't experience this at all. Maybe our SharePoint/OneDrive is better managed, maybe something else is going on, but I have not yet encountered a single time of multiple versions unless someone was explicitly copy and pasting the file to make versioning in their own dumb system. Which, the same dumb thing could be done in Google Workspace. Don't have people copy and pasting the file all over the place and you won't…

Our SharePoint was not really managed when we moved to Teams - we didn't use it (mostly because it's such a horrible product that has no clear vision behind it). But Teams started filling up stuff there all over the place.

In the end we did need to use it because we moved from another storage service to OneDrive (another "quick win") for a manager and OneDrive is really bad at team-owned storage, it's really for personally owned files only.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#675

Post by catfishx »

freeqaz wrote: post #380

Teams for Linux, when I inspect it with htop, is actually running a process called "Skype" in the background. I think that explains some of the crappiness of the UX! (It has required some serious hacking to make it even functional for me.) Since then my team has swapped to using Discord for what we're doing. It sounds a bit weird to use a Gamer tool at work but it's actually been pretty great since we run an Open Sou…

On my machine teams regularly eats up several gigabytes of ram, even when not interacting with it at all.

I generally don't care about applications using a lot of ram, but this is just too much for a program which I mostly use for text messaging.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#676

Post by d1sxeyes »

ska wrote: post #637
foobaw wrote: post #634

Earlier quoted context omitted.

400,000+? I don't mean to question this but that's a crazy high number assuming it's not Amazon or Walmart.

At a guess there's at least 20 companies with head counts that high, and most of them aren't tech and retail.

Much much more than that in case OP is not in the US.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#677

Post by xnx »

jacquesm wrote: post #194

Teams is so horrific we banned it. If you force us to use teams you'll have to find another supplier. Seriously, it is incomprehensible that Microsoft would ship something so utterly broken. I know they don't have a reputation for writing good software but Teams is on another level, and I don't mean that in a positive way. I've really tried to get it to work but it is so messed up that I don't think it can be done. M…

Lack of interoperability in chat and video conferencing reminds me what a miracle it is that email has worked so reliably and consistently for 40 years.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#678

Post by rs999gti »

luckman212 wrote: post #584
generalk wrote: post #421

Regardless of what you think of Teams -- I myself have had nothing but poor experiences over 2.5 years of using it daily -- it's telling that Microsoft has to require folks to use Teams. I'm sure this is just Microsoft unifying everyone on the same comms platform, but seriously, I don't know anyone who chooses Teams. I know non-tech folks who chose Outlook 365 because of familiarity and then end up on Teams because i…

It's boring reading comments like these. Really? 2.5 years of " nothing but poor experiences"? I have to ask: what the hell is wrong with your computer? I started using Teams heavily in 2020 and yes, back then it was unequivocally the worst of the bunch. But I've seen it make great strides, and it's been many months, perhaps years since I've really had any problems with it. Audio, video, screen sharing, PSTN dial-in,…

> I have to ask: what the hell is wrong with your computer?

For our org, it isn't the PC, it is the org controlling Teams and the firewall.

They have Teams configured somehow, that none of the subsidiaries can talk to each other, you can't talk to outside people or invite them, and the performance is really bad due to the way the clients and firewall are configured.

I'm guessing lots of orgs are in the the same boat because Teams is newer than Zoom, Web Ex, or Go to meeting, and for these legacy meeting clients the PCs, firewall, and org has had time to optimize for them.

Teams is more of an afterthought because it comes with 365.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#679

Post by HeavyStorm »

What most people in this thread don't realize is that Teams, like most products sold to CIO, don't have to be good for it to succeed.

Instead of an stellar ux, Microsoft is focusing on what sells it - that seamless centered experience that unifies SharePoint, Power, replaces slack and Discord and everything else in a single app.

It sucks, but it sells, because people buying it aren't the core users.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#680

Post by HeavyStorm »

generalk wrote: post #421

Regardless of what you think of Teams -- I myself have had nothing but poor experiences over 2.5 years of using it daily -- it's telling that Microsoft has to require folks to use Teams. I'm sure this is just Microsoft unifying everyone on the same comms platform, but seriously, I don't know anyone who chooses Teams. I know non-tech folks who chose Outlook 365 because of familiarity and then end up on Teams because i…

That's a lot of naivette. Corporations _require_ we use stuff everyday. And when that stuff is something you build yourself, it makes zero sense that github is still using something else.
Post reply on HN