GitHub Slashes Its Entire Engineering Team in India (techcrunch.com) 32
GitHub, the popular developer platform, has laid off virtually its entire engineering team in India as the Microsoft-owned firm cuts its expenses amid weakening global market conditions. From a report: The developer firm has eliminated over 100 jobs in the South Asian market, a person familiar with the matter said. GitHub informed the employees about the job cut on Tuesday.
AI? (Score:1)
Re: (Score:2)
hindi.
looks like chat g p t has a language translator question answer set
Seen the risk back when master branches were taboo (Score:5, Interesting)
Does anyone still use it? Mandatory 2fa preventing all the useful quick pushing/pulling from scripts without setting up annoying static creds.
My big scare was the forced removal of master branches back when that was all the rage. I just cant see using it for business use and have instead hosted my own gitlab servers which have been just fine.
I am scared of all this meddling. Who can build around something like this?
Re: (Score:2)
Re:Seen the risk back when master branches were ta (Score:5, Funny)
It was really funny for us Slavs to repent for slavery by removing master/slave.
Re: (Score:3)
I care its annoying, on my little project its not worth the bother. AcidFnTonic also cared, while not proof that a significant portion cared or didn't care, neither is your observation that nobody cared (I am reinterpreting it as no significant amount of peopled cared since nobody cared is clearly wrong).
The thing is they didn't ask, if everybody is after that then why not put up a box saying do you want 2 factor authentication turned on on your project, the user can say yes or no. You could also put up a
Re: (Score:3)
No forced removal, main just became the default (Score:1)
No forced removal, main just became the default for newly created repositories. You can still have a master branch.
Re: (Score:2)
It doesn't even create a branch by default - you get a completely empty repo and you can push whatever initial branch you want to it. I just recently created an organisation-level repo and pushed a master branch to it a few days ago with no issues whatsoever.
Re: (Score:2)
I think you're suppose to call them "main" branches now.
Re: (Score:2)
"I just cant see using it for business use and have instead hosted my own gitlab servers which have been just fine."
So you operate servers, that themselves need maintenance, updates, hardware refreshes and failure recovery, security updates, gitlab version updates, and of course backups, and then those backups also need to be maintained and verified.
Sure that sounds like less work than the 2 seconds it took me to switch MFA on on github. I was already using permission configured access tokens with my script
Re: (Score:2)
Re: (Score:3, Insightful)
They finally realized the mistakes they make cost a lot more than a qualified and skilled engineer.
Re: (Score:1)
So is this an admission that engineers are not so fungible after all?
Re: (Score:2)
Sliver Linings (Score:4, Insightful)
At least there will be fewer meetings at very late or very early times of day.
I dream of working in a place where everyone is in the same timezone.
Re:Sliver Linings (Score:4, Insightful)
We would always meet with our offshore team in the morning. By end of our day we would ensure they had proper instructions and details of where we left off. In a way it made it feel like we had round-the-clock work being done.
Granted, this means there has to be very good leadership and communication being performed on both sides. And more times than not this is not the case. This is why people have bad views of offshore teams. But it is the companies involved (on both sides) that are the problem as they often put non-technical people to lead from onshore a group of offshore technical people. The communication is almost non-existent and confusion quickly sets in to the projects.
Re: (Score:2)
I have colleagues around the globe. There is no good time of day to have a meeting with say US, India and Malaysia. Someone is going to be meeting very early or very late in the day.
'git prune' then? (Score:3)
new jobs (Score:3, Informative)
Not a problem. They will find new jobs writing code for scam call centers.
Re: (Score:1)
Re: new jobs (Score:1)
This might come as a surprise to the resident dumbasses but engineers have already been relocated into other Microsoft divisions and offices were closed already. This is a cost cutting measure and only support staff would still be remaining github. Github hired people to migrate it's stack to Azure and nothing else is planned for it so it makes sense to cut cost.
For what it's worth, most firings have happened in USA and India center is still hiring.
Re: (Score:1)
Noshoring, MsGPT runs the show now
Google picks up GitHub layoffs? (Score:1)
Re: Google picks up GitHub layoffs? (Score:2)
IBM vs. GitHub (Score:2)
Interesting... A few years back IBM cut engineering jobs in North America and handed them to India, but today GitHub cut those jobs in India and kept the North American ones, which kind of supports what most folks think about IBM these days: They've been getting it wrong for a very long time.