Earlier quoted context omitted.
They fired a ton of employees with no rhyme or reason to cut costs, this was the predictable outcome. It will get worse if it ever gets better. The funny thing is that the over hiring during the pandemic also had the predictable result of mass lay-offs. Whoever manages HR should be the ones fired after two back to back disasters like this.
And yet we keep paying the company
GitHub: Git operation failures
61–70 of 335 posts
Re: GitHub: Git operation failures
#62Re: GitHub: Git operation failures
#63Re: GitHub: Git operation failures
#64Re: GitHub: Git operation failures
#65Re: GitHub: Git operation failures
#66I thought I was going crazy when I couldn't push changes but now it seems it's time to just call it for the day. Back at it tomorrow.
Re: GitHub: Git operation failures
#67A. Are these major issues with cloud/SaaS tools becoming more common, or is it just that they get a lot more coverage now? It seems like we see major issues across AWS, GCP, Azure, Github, etc. at least monthly now and I don't remember that being the case in the past.
B. If it's becoming more common, what are the reasons? I can think of a few, but I don't know the answer, so if anyone in-the-know has insight I'd appreciate it.
Operations budget cuts/layoffs? Replacing critical components/workflows with AI? Just overall growing pains, where a service has outgrown what it was engineered for?
Thanks
Re: GitHub: Git operation failures
#68Why are there outages everywhere all the time now? AWS, Azure, GitHub, Cloudflare, etc. Is this the result of "vibe coding"? Because before "vibe coding", I don't remember having this many outages around the clock. Just saying.
Re: GitHub: Git operation failures
#69Re: GitHub: Git operation failures
#70Obviously just speculation, but maybe don't let AI write your code... Microsoft CEO says up to 30% of the company’s code was written by AI https://techcrunch.com/2025/04/29/microsoft-ceo-says-up-to-3...