The worst part of this is that everyone at GitHub is now forced to use Microsoft Teams.
GitHub to lay off 10% and close all offices
301–310 of 907 posts
Re: GitHub to lay off 10% and close all offices
#302Fortune now confirming: https://fortune.com/2023/02/09/github-is-laying-off-10-of-st...
>i) Effective immediately, we will be moving laptop refreshes from three years to four years. ii) We will be moving to Microsoft Teams for the sole purpose of video conferencing, saving significant cost and simplifying cross-company and customer conversations Layoffs and having to use teams? Talk about a morale hit
Re: GitHub to lay off 10% and close all offices
#303Earlier quoted context omitted.
this is terrifying. for all the grief people give Slack, I've used both and I would seriously consider leaving a company that expected me to use Teams long term.
Can someone give me the TLDR on why they hate teams so much? I suppose I work in an organization with few true "technical" folks, and everyone is under Microsoft licenses so it doesn't seem like that big of a deal. I've used both slack and teams. What am I really missing out on here?
For a more detailed take:
Slack is far from perfect but Slack is generally clean, quick, simple and compact. Slack feels like a purpose built tool for chat. Even when they add stuff like huddles it never feels like the priority is anything but the chat. When they roll out updates that make typing or formatting jankier I find they often get a fix out quickly.
Teams feels like it is doing a little bit of everything and is slower, wastes screen real estate, has poor UX all over and does a lot of things so-so to decent vs. one thing really well. Why is chat so different in a Teams/Chat vs a Teams/Teams/Channel? You can't even do the same markdown formatting in those places. And speaking of markdown, you can type a backtick around a string to monospace it like in slack but if it's at the end of your message it won't format it. You need a trailing space for it to kick in the formatter. Little details matter and a lack of attention to them as an organization makes bad UX and weird behavior leak into your software.
Re: GitHub to lay off 10% and close all offices
#304When I visited the GitHub office in SF in 2017, it was nearly empty. Given how extravagant and beautiful it is, it struck me as a colossal waste of money even then.
Re: GitHub to lay off 10% and close all offices
#305I am absolutely certain this is to suppress wages and employee rights. It is a coordinated effort across the industry and should be immediately investigated.
Re: GitHub to lay off 10% and close all offices
#306Earlier quoted context omitted.
Because when you saw it you walked 360 degrees away
360 is a full circle, e.g. you'd turn right back toward it.
Re: GitHub to lay off 10% and close all offices
#307The worst part of this is that everyone at GitHub is now forced to use Microsoft Teams.
Re: GitHub to lay off 10% and close all offices
#308Earlier quoted context omitted.
I'm quite confused because almost all conversation in my company's slack happens in threads. Maybe your impression of Slack was formed in a time when they didn't have threads?
I'm also confused because almost all of my company's Teams usage happens in unthreaded chats.
Re: GitHub to lay off 10% and close all offices
#309Re: GitHub to lay off 10% and close all offices
#310Earlier quoted context omitted.
How is this the worst part lmao?
You've clearly never used Teams. But in all seriousness Teams is fine for chat and video.
What am I missing?