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

131–140 of 725 posts

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

#131

Post by drewda »

mhardcastle wrote: post #117
kimbernator wrote: post #72

How is it possible that Teams is still such a poor product? I really didn't like it when my job switched like 6 years ago, and I don't recall ever feeling that it improved in any meaningful way. I switched jobs to one using Slack and it's not perfect but it is a lot better. It's almost a meme at this point. In the presence of other clients that have gotten it "right" (or at least more "right" than teams) like Slack,…

I don't disagree with the limitations of Teams, but Microsoft improved their video call/conferencing software substantially when they moved from Skype for Business to Teams. At least things haven't been entirely stagnant.

Yes, I will give Microsoft that -- MS Teams is so much better than Skype for Business/Lync, which was a horrible piece of video conferencing software.

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

#132

Post by jdlyga »

We used Teams for video occasionally back in 2019 before the pandemic. It was pretty unreliable, and had much better success with BlueJeans or Zoom. If there were more than a couple people on camera, Teams couldn't handle it the same way Zoom or BlueJeans could. I haven't taken a second look since then.

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

#133

Post by OJFord »

aldarisbm wrote: post #36
yamtaddle wrote: post #29

Earlier quoted context omitted.

Slack has video conferencing. Every redundant tool a company makes workers use makes work less pleasant. I'd expect at some point they'll push them the rest of the way onto Teams, to reduce that redundancy. Which will be even worse, because Teams is so incredibly bad.

Slack's video conferencing is archaic compared to something like zoom (maybe not teams), but out of all of the video conferencing tools, slack is the worst.

It's at least a decade ahead of Zoom on Linux. The latter's like using 00s Skype.

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

#134

Post by bcrosby95 »

w0m wrote: post #50
ralph84 wrote: post #11

Somewhat ironic that a company that’s entire existence was based on the idea of giving developers great tools no longer values giving its own developers great tools. Only a matter of time before this new attitude towards developers shows up in the product.

That's overtly harsh take I think. Teams has issues; but asking employees of a company to use said companies tools internally isn't necessarily a bad thing. Hard to improve without dogfooding.

So should they also force every subsidiary to use Windows, VSCode, Office 365, Azure, etc?

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

#135

Post by evancox100 »

creshal wrote: post #98
bombcar wrote: post #34

Earlier quoted context omitted.

The problem is that what GitHub does is relatively reproducible (Gitlab, gitea, bitbucket? others do it) but the value GitHub provides is free hosting for so much content. Anyone can make an image hosting site, making one profitable long term is always the problem. For now, GitHub is winning because of the free side of their toolset.

I'm fairly sure Microsoft doesn't even have the ambition to make it profitable. Like Youtube for Google, or costco hotdogs, it's to get a foot in the door (or rather, customers' feet in your doors) to upsell people on all your other products.

Why do you think YouTube isn’t profitable? Plenty of ads in it and bringing in something like $15 bln/year in revenue. Don’t know exactly the COGS, etc., but hard to say they aren’t making money. Android is probably a much better example than YouTube.

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

#136

Post by [deleted] »

kahrl wrote: post #51
chongli wrote: post #2

That’s plenty of time to dust off the resume and start pounding the pavement! Very generous of Microsoft to give so much notice! Edit: for those who may think I’m overreacting to a small change in tooling, I offer this classic essay [1]. It explains the reasoning behind leaving much better than I could! [1] https://steveblank.com/2009/12/21/the-elves-leave-middle-ear...

[flagged]

[deleted]

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

#137

Post by apnew »

w0m wrote: post #50
ralph84 wrote: post #11

Somewhat ironic that a company that’s entire existence was based on the idea of giving developers great tools no longer values giving its own developers great tools. Only a matter of time before this new attitude towards developers shows up in the product.

That's overtly harsh take I think. Teams has issues; but asking employees of a company to use said companies tools internally isn't necessarily a bad thing. Hard to improve without dogfooding.

Literally sitting here right now trying to figure out how to get simple things going compared to slack after being forced to move to teams from slack (not GitHub).

I am all for dogfooding here, but if the dog-fooding is not improving the product it shows that the goal is to eat market because of lopsided ecosystem monopoly. Screw MS and MS Teams.

eg. : We need a tag in a shared channel so that we can provide single point of support for other teams, instead of people having to tag the whole channel. Slack made is as easy as breeze to sync on-call person from PD -> a group.

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

#138

Post by jrochkind1 »

gautamdivgi wrote: post #129
ralph84 wrote: post #11

Somewhat ironic that a company that’s entire existence was based on the idea of giving developers great tools no longer values giving its own developers great tools. Only a matter of time before this new attitude towards developers shows up in the product.

My Teams works fine on my Mac without issues. Have been using it for over a year now. Fwiw - I don’t understand why it’s hated. It’s a collaboration tool - mainly messaging and conferencing. It’s been decent at that for me.

Teams works relatively fine for me now that I upgraded to an M1 macbook pro. (Still occasionally crashes for no reason, but no apparent performance problems).

A year ago I was still on a 2015 Macbook, and it was still doing just fine for me on everything but Teams, Teams was a disaster, it would freeze and drop video all the time, or have perceptible delay between click and effect.

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

#139

Post by sofixa »

gautamdivgi wrote: post #129
ralph84 wrote: post #11

Somewhat ironic that a company that’s entire existence was based on the idea of giving developers great tools no longer values giving its own developers great tools. Only a matter of time before this new attitude towards developers shows up in the product.

My Teams works fine on my Mac without issues. Have been using it for over a year now. Fwiw - I don’t understand why it’s hated. It’s a collaboration tool - mainly messaging and conferencing. It’s been decent at that for me.

Because it's by far the worst UX-wise. If you know better tools, it's just shit. To add insult to injury, it kind of sort of works, sometimes, but there are tons of small problems here and there all the time in many cases. I had to use it only for video calls for 3 years, and probably weekly there was something wrong like restart needed because it screwed up my audio.

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

#140

Post by kypro »

mhardcastle wrote: post #117
kimbernator wrote: post #72

How is it possible that Teams is still such a poor product? I really didn't like it when my job switched like 6 years ago, and I don't recall ever feeling that it improved in any meaningful way. I switched jobs to one using Slack and it's not perfect but it is a lot better. It's almost a meme at this point. In the presence of other clients that have gotten it "right" (or at least more "right" than teams) like Slack,…

I don't disagree with the limitations of Teams, but Microsoft improved their video call/conferencing software substantially when they moved from Skype for Business to Teams. At least things haven't been entirely stagnant.

The 3 companies I've worked for over the past 5 years have used Slack for chat and teams for meetings. and to be honest that's my preferred way to work too.

Huddles are okay for internal 1-on-1 meetings, but Teams works well when you need to organise a large meeting (potentially with people outside your org).

On the other hand Teams is awful for chat. Slack has put so much care and thought into messaging that their UX is close to perfect imo.

Post reply on HN