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

401–410 of 725 posts

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

#401

Post by ralmidani »

kypro wrote: post #185
ralmidani wrote: post #97

I’m extremely picky - as long as my livelihood is not threatened and I actually have options. For me, being forced to use Windows, Teams, Skype, Java/Spring, or Jira (among others) would be a dealbreaker (again, unless that job might be among the few available to help me feed my family). I spent some time learning in the structured environment of a large company, which I recommend everyone do for a first and/or secon…

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 what we use at my day job), and on the other hand would actively avoid a job that required more than a trivial amount of C++, Java, or server-side Node.js. I would be OK with the rest (and probably also Rust and Go, although I haven’t learned enough to be sure). For code hosting, I prefer GitLab and am OK with GitHub (for now at least). For tasks/issues I’m OK with Asana or GitHub and only avoid Jira. For IDEs I prefer Sublime but would be OK with whatever. For OSes, I prefer GNU/Linux, can live with MacOS for now (but the experience is degrading rapidly), and only really avoid Windows.

I totally believe we should normalize devs having requirements for what kinds of jobs they will consider (including tech stack and tools, but also industry, company size, culture, location, etc). Especially if we’re OK with companies having wishlists which are often far longer and more rigid.

Also, for what it’s worth, I speak/write English and Arabic natively, and have a genuine desire to learn Spanish, Kurdish, and Japanese.

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

#403

Post by mrguyorama »

blibble wrote: post #342
wvenable wrote: post #218

Earlier quoted context omitted.

It's so weird -- I use Teams all the time and I've never had a serious problem with it. It's not the greatest software ever made but it's certainly functional. It's definitely getting a lot of work done to it.

I tried hiding a channel once that was it, there's apparently no way to ever get it back unless I can remember its exact name (which I can't) I learnt my lesson

Uh what? Every "Team" I have on the left side of my teams window has a "X hidden channels" message that I can click and that shows every single channel in the teams, including archived ones.

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

#404

Post by charrondev »

addandsubtract wrote: post #362
javier123454321 wrote: post #289

Earlier quoted context omitted.

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.

I feel like a lot of it comes down to which system & client people use. If you're on PC or macOS and using the desktop client, you're probably having a good experience (as long as you only have one account). If you're on Linux or use the web version, you're probably going to have a bad time.

Unfortunately the Mac client is similarly awful. Absolutely horrifically slow. We were using for a little while at my company after we were acquired and it had so much horrifically buggy or slow behaviour.

- Switching between chats caused a big flicker of content loading in. I have no idea why this wasn’t cached but it was annoying. - starting a meeting could sometimes takes 30+ seconds. - I frequently observed and issue where some hidden/invisible window would be opened in the background and keep taking focus every time a used the tab key to cycle through windows. - Delayed and sometimes missed notifications. Why they didn’t use the native system notifications was beyond me. The notifications also did not respect the systems do not disturb window. Sometimes they would appear behind other content and would be missed. - massive resource consumption. Our 1 teams org would frequently be consuming > 3gb of memory on my system. People complain about slack but this is a whole other level.

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

#405

Post by VBprogrammer »

LeSaucy wrote: post #383
0cf8612b2e1e wrote: post #269

Earlier quoted context omitted.

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.

Search is horrendous. There are strings that I am guaranteed to have written and it is unable to find them, nevermind the ui for it is absolutely unusable.

Search is easily the worst. Video performance was pretty Terrible pre-covid but seems to have improved to the point of not usually a problem.

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

#407

Post by prmoustache »

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…

I find it strange to associate open source and discord. I tend to dismiss any open source project that uses it.

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

#409

Post by stuaxo »

wvenable wrote: post #218
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…

It's so weird -- I use Teams all the time and I've never had a serious problem with it. It's not the greatest software ever made but it's certainly functional. It's definitely getting a lot of work done to it.

The Linux version of Teams was very broken for ages, but instead of fixing it, they dropped it.

So much for the cross platform Microsoft.

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

#410

Post by gnicholas »

samiru wrote: post #196
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 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 occasionally use Teams on my Mac and am dismayed that every time I open it, it reinstalls itself in my Login Items. In my book, that qualifies it as malware. I used the desktop version for a while, to see if they would update it and fix this bug. Turns it out it was a 'feature' not a 'bug'. Now I just use the web version, and plan to never reinstall the desktop software again.
Post reply on HN