401–410 of 907 posts
The worst part of this is that everyone at GitHub is now forced to use Microsoft Teams.
The worst about teams is that they still haven't implemented a corrected markdown editor. Its a pain to copy code into it
Earlier quoted context omitted.
I don't see where is that a problem? People who will be using Teams are people using Office 365 daily. Having a cohesive ecosystem makes complete sense. From a UX too.
The problem is that Teams is used by companies who have IT departments that do absolutely insane things like DELETE THE CHAT HISTORY AFTER 24 HOURS because of some sort of perverse, contrived "security" issue. These are the morons that Microsoft is selling to, and giving advice to as on how to configure it. So you wind up with a system that's almost worse than not having anything at all. Our Sharepoint installation w…
This really is the techpocalypse, huh? I’m young (35) but I’ve never seen layoffs so continuous. I wonder how far into the year this will go and if we’ll ever come back. Maybe companies truly will start offshoring.
> "I wonder how far into the year this will go and if we’ll ever come back." We'll be back, but not until the industry discovers something of actual value. My internal narrative of all of this is that many of us came up during the smartphone revolution which legitimately created a ton of new value. Products that could not exist before now could (and did!), resulting in a flurry of new companies, new products, and new…
AI has the property that it can reach all the people around the world. From AI that teaches you a foreign languages to automated advisors that can e.g. recommend a diet based on your needs or even AI dating where instead of sweeping AI will do the match (I would pay for the last option).
The problem with AI is that there was already "AI winter": high expectation in the beginning, but nothing workable delivered in the end in the late 70s if I remember correctly. I hope it will not end up like this, this time.
I also don't see much potential in metaverse. For one we are crazed about healthy lifestyle and siting with glasses to walk though some virtual landscape makes no sense to me. It will only make you weak and tired. For the second the tech is not there yet, we may fool our sense of vision and hearing, but we cannot fool our sense of orientation, neither our muscles.
The worst part of this is that everyone at GitHub is now forced to use Microsoft Teams.
"We will be moving to Microsoft Teams for the sole purpose of video conferencing"
Earlier quoted context omitted.
It’s disturbing to think that people think human connection is irrational. I guess y’all forgot that that was how labor unions were formed.
Most of the history of labor unions involved meeting in secret in venues outside of work's control. Very few labor unions were ever formed in the halls of an office building. Also, human connnection isn't irrational, but expecting all or most of your human connections to come from your job may be.
I was responding to that part. Office create a rational connection in an irrational setting.
My grandfather and most of my great uncles were coal miners in Shamokin, Pennsylvania. They all talked about unions and striking in the mines. And they formed close bonds which made going on strike much easier as well as created a huge social bond when they where striking supplying each other with food and pirated coal.
Earlier quoted context omitted.
> 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. This move will be complete by September 1, 2023. We will remain on Slack as our day-to-day collaboration tool.
I really love when one brings in more tools. So let's use Slack for text, Teams for audio and Zoom for video. It's like most people forgot that in the early days there was a phone and it worked just perfect. Everyone was reachable through it. Now I need to check multiple channels for the same thing.
Interesting about the offices. Is it because they are merging with MSFT even more or because they are embracing a remote-only philosophy?
That was my question as well. I wonder if they'll phase out the GitHub offices, then, after a time, force workers to RTO to existing MSFT offices.
An observation, Microsoft subsidiaries are being told to use teams. Cisco subsidiaries are being told to use webex in place of slack. We might be in a new world of chaos
Earlier quoted context omitted.
>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
I wonder why they are not talking about the elephant in the room, the AWS spend. Cut back on that and these layoffs probably aren't necessary. The problem is the sheer size of GitHub data and the unreliability of Azure. There is an entire datacenter that is unused because data locality severely limits performance.
Earlier quoted context omitted.
If I were forced to use teams I would quit. At least if you're laid off you get serverance
>>If I were forced to use teams I would quit. It's funny to hear this because if I were looking for a job one of the selling points for me would be if they used teams. I'm on it all day, I present and run video meetings on it. I use it on different devices. It's not perfect by any means, but I'm confident that it will do what I need it to do. My only guess is you're on a linux desktop and you don't use an enterprise…
About the only thing I can say in its favour is that I've rarely had trouble with video or audio quality.
It is an unbelievable performance hog. It launches something like 8-10 processes, one of which defaults to running at above normal priority. Despite this, frequently text chat messages will lag ~30 seconds between notification and appearing in the actual chat window. Even clicking on UI elements like buttons will often have a lag of 5-10 seconds. If I'm on a video call, it uses more CPU than any other process, including my browsers (~50 tabs open across ~10 windows) and a Kali Linux VM running in VMware Workstation.
The UX is awful. For example, there is no way to permanently reorder the list of channels you're in (not even sorted alphabetically). It's always the order you joined them every time you start up Teams. My list of channels is something like 50 long, so I basically just have to search for the one I want, because the alternative is to scroll through the list and read every line.
There are bizarre bugs. Sometimes I'll join a video call, but it will be a "ghost call" where I can hear the participants, but there's no window for me to interact with, so all I can do is close Teams entirely and start over. Sometimes I won't be able to unmute myself, so everyone will wonder why I'm not responding. Today I saw a new one where random members of the call had their video feeds replaced with empty black space (no profile photo/letter).
It's unbelievable to me that I could use IRC, MSN Messenger, and any number of other chat apps on a PC 20+ years ago and get a snappy response time, and yet Teams still feels like it's mired in a swamp running on hardware that's something like 100x faster and with 20-50x the amount of RAM.
Something like 15 years ago, I was troubleshooting a SharePoint issue and discovered that even though it was using a SQL Server database to store everything, instead of taking advantage of the power of a good database design and platform, all of the kind of object affected by the problem were stored as enormous XML blobs inside a single column, with SharePoint doing a SELECT * and then acting as its own terrible inner faux-database layer. I have to imagine that Teams is a similar "don't ask how the sausage is made" kind of situation, where MS basically shipped an early prototype instead of productionizing it.