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

281–290 of 725 posts

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

#281

Post by matwood »

moonchrome wrote: post #177
mullingitover wrote: post #155

Earlier quoted context omitted.

> How is it possible that Teams is still such a poor product? List of products Microsoft makes: - [bajillion item list of everything including the kitchen sink] List of products Slack makes: - Slack Microsoft gives Teams away for free and to them it's worthless. They have no incentive to make it great, just good enough that you'll look at the price of Slack, look at the price of Office 365, and say "ehh, we can save…

>Making Teams not suck doesn't move their revenue dial one iota. That's not true, I would switch to Office 365 if it didn't suck. Having an entire suite fully integrated and under one license is a great value proposition - but the thing has to work. I've had to use Teams over the years and every time I get the same shitty experience I've had with it 5 years ago when I first tried it.

> I would switch to Office 365 if it didn't suck.

From what? O365 collaboration is terrible. If you do joint document editing, O365 will drive you nuts after using something GSuite. What many do is have GSuite and then O365 for people who need office products for various reasons.

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

#282

Post by xattt »

wvenable wrote: post #237
xattt wrote: post #219

Earlier quoted context omitted.

Your definition of broken is likely different than the GP.

Broken means "doesn't work". I've used Teams for 2 years now for conferencing, chat, desktop sharing, etc. It works just fine. I think a lot of Microsoft hate is clouding judgement here. People want Teams to suck.

My broken is fixing something all the time in order to get it to work correctly.

Why does Teams occasionally load up with the usual icons showing the broken image icon? Why did my organization create a special “Fix Teams” utility?

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

#285

Post by amaccuish »

0cf8612b2e1e wrote: post #269
wvenable wrote: post #249

Earlier quoted context omitted.

What does it mean to be worst-in-class for text chat or video conferencing. Video conferences look and sound great. Text chat is text chat. What am I missing here that's so awful?

For chats, it is embarrassingly slow at rendering. Seemingly only maintains the last ~two dozen messages in memory, if you scroll back in history, you have to painfully wait for it to retrieve the text and then render it. Weird rendering bugs frequently. Meanwhile, I remember reading full ebooks on my Pentium which were rendered as a single HTML file with zero lag.

I have the same problem with Slack, unsure why Microsoft needed to copy the pitiful performance. That the Slack mobile apps mirror the non-existent reliability of the desktop clients is actually pretty amazing.

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

#286

Post by ricktdotorg »

top_sigrid wrote: post #85
yamtaddle wrote: post #74

Earlier quoted context omitted.

It's so bad it makes Slack look lightweight. Which is a real accomplishment.

Actually true and a good way to put it

the best way to use Slack on any desktop/computer OS is: 1) login to Slack in a chrome browser tab and then --> Create Shortcut 2) uninstall Slack app

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

#287

Post by ccosmin »

revscat wrote: post #147

To everyone at GitHub: I’m so sorry. I don’t mean this in a clever way, either. Teams is awful and it will make your lives worse to one degree or another.

I do use it a lot. Some of the infuriating things: * scrolling back past last day conversation doesn’t work properly, you have to wait a few seconds then text is rendered in such a way that you lose track where you were * worse latency with each month for receiving messages. I’m logged on multiple machines and messages come with random delays * even after joining a call my other Teams instance will still ring for some time…

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

#288

Post by ricktdotorg »

shagie wrote: post #200
IceWreck wrote: post #179

What did GitHub staff use before ? Slack + Zoom ? Mattermost or something else ?

If I've read the histories and articles correctly, Slack for intracompany chat and Zoom for intra and inter company video. This is switching the intra and inter company video to Teams (which means that GitHub doesn't have to pay Zoom for video anymore). Intracompany text chat remains on Slack.

Slack [video] Huddles didn't cut the mustard for them?

edit: ahh i see "inter-company". yeah, Slack huddles start to suck when guest accounts/other Slack instances or externals get involved. got it.

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

#289

Post by javier123454321 »

ygjb wrote: post #209
samiru wrote: post #196

Earlier quoted context omitted.

I wonder if those who complain about Teams actually use it. They might not. My company forces us to use Google Chat. I would take Teams any day.

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…

I simply don't understand this at all.

I've used in 3 of my last workplaces. Two exclusively and one in addition to slack. No particular complaints for having internal meetings of any size. I literally do not know what you are talking about and feel like I am missing something.

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

#290

Post by chongli »

red-iron-pine wrote: post #143
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...

Tech layoffs are exploding and there is a looming recession and maybe world war, and you're gonna quit over the work-chat software? At least the layoffs meant people got severances; this is walking for $0 and maybe the ability to find a different office productivity suite. I mean vote with your feet and all, but if this came up in an interview I'd probably laugh at you.

There’s a big difference between pulling a George Costanza and quietly talking to recruiters at other companies. Don’t make a scene, just look for a better job and give notice when you get an offer.
Post reply on HN