Live data from Hacker News

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

twitter.com

651–660 of 725 posts

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

#651
post #217

Earlier quoted context omitted.

What's the issue with zoom? I think it's one of the best software I have on my machine. It never ever stopped working since I have it installed, not even in meetings/webinars with 1000+ people. And the integration with Slack is really convenient, you can start a meeting in seconds anywhere you are.

On what operating system?

99% of the time: Mac.

From time to time: iPhone, iPad, android phone, android tablets, windows.

I hear from colleagues having Linux that the OS might indeed be an issue sometimes, they have to restart the system, etc.

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

#652
post #539

Earlier quoted context omitted.

Shameless plug: that's why we started FossTeams [1]. As most of us are forced to work with this thing, the least we can do is to find a workaround for the problem somehow... [1]: https://github.com/fossteams

You’ve mentioned this app before, last I checked there isn’t a usable client yet. Are you just hoping to get more FOSS devs on board or has something changed?

The first one, for now I'm a solo developer on this thing :(

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

#653
post #196

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 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.

Whoever used WebEx would treat Teams as the coming of the messiah.

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

#654
post #220
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 use it and I would be happy if Teams was able to do basic copy/paste. When you copy, it copies things you didn’t select and doesn’t copy some things you selected. When pasting, it auto-formats the text and does a terrible job at it. It’s a disaster. I hope the Teams team is forced to use Teams.

Not intuitive at all but there is "ctr+shift+v" for pasting only text

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

#655
post #185

Earlier quoted context omitted.

It's interesting you say this. I've always felt my flexibility was a strength and quite enjoy being asked to use new tools and software. To be honest I tend to look quite poorly on people unwilling to provide flexibility on the tools they work with. In my experience it can be quite disruptive when you have one highly opinionated team member who will refuse to work with a new tool because of a personal preference. I g…

I said I’m extremely picky, but the list of things I would be OK using is much longer than the list of things I would not work with unless circumstances forced me to. Maybe I should have also said I’ve learned and/or dabbled in/used Python, Ruby, C, C++, Java, JS (server-side and client-side), CoffeeScript, TypeScript, and Elixir. I currently have a strong preference for working with Elixir (and fortunately that’s wh…

Hi ralmidani, I recognize being picky like that with tech choices.

My friend and I are developing a product to enhance the job search process. Especially for devs that want to be very specific on what tech they do and don't prefer to work with.

May we ask you a couple of questions? I know you're not searching for a job (kudos on finding an Elixir job) but I think your input would be valuable.

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

#656

Earlier quoted context omitted.

I think the biggest problem with Teams is the leadership's strategy. They seem to be focusing on adding as many glossy features as quickly as possible. The quality, performance and consistency doesn't seem to be a point of consideration at all. Yet for a user who spends a lot of time in it each day, I really don't care about animated waves on top of my video, or this together mode. I just want it to work and not take…

It's CDD, checklist driven development. When you are competing against another product in the enterprise space the people making the decision probably won't be using what you are selling often but they will look at the list of features, so money spent adding new features is more important and higher prioritized than stability reliability or any other nonfunctional requirement.

I see, but I doubt that makes sense here though.

The main selling point for teams is that it's free for existing M365 customers. Microsoft is aiming specifically at a "quick win" for IT managers to cut a competing product and replace it with something they're paying for anyway.

And usually the top would spend a lot of time in meeting themselves too, it's not something they won't be using themselves.

But I know what you mean, in our company the top execs have their own support team so they don't even know how bad our outsourced support is. A lot of production issues are streamlined for them because of this.

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

#657
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.

If Microsoft is serious, this is a great chance for trickle up. Give an org that has been using Outlook Teams and they won't have any suggestions, give it to an org using Slack and the feedback will be immense. I admit to getting caught up in the Microsoft is innovating hype from recent news but would not be surprised if they finally start to really iterate and improve on their cruft going forward. Dogfooding in the GitHub org just makes a lot of sense.

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

#658

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,…

Teams was introduced less than 6 years ago ;)

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

#659

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 sort of agree, teams are working really well for us, a medeium sized globally dispersed team of developers.

I do have one pain-point: my phone discord sometimes does not understand that it should be quiet if I am active on a computer at the same time, and dings for very new chat message.

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

#660
post #245
post #235

Earlier quoted context omitted.

Likewise, I don’t particularly like it but it’s fine. My biggest gripe is nonexistent official Linux support - I hate having to use a package maintained by one person on GitHub to get a desktop application for Linux, when this application is so critical for my day to day. But besides that it works fine.

The Linux app doesn't even support screen sharing when you're using Wayland. I was forced to try out the browser based variant (meeting link opened the web variant instantly instead of giving me the choice to use the app instead) and can now finally share my screen (even single windows!). Also I can now use backgrounds, which the app didn't support.

That always frustrated me, even more-so considering how that volunteer-built package I mentioned (https://github.com/IsmaelMartinez/teams-for-linux - an Electron build of the web app, nothing flashy but does the job just fine) does support screen sharing. I haven’t checked whether it supports backgrounds as I only use voice when on calls, but I’m guessing it does if the browser variant does.
Post reply on HN