Comment by guywithabike
9 hours ago
It's notable that they blame "our upstream provider" when it's quite literally the same company. I can't imagine GitHub engineers are very happy about the forced migration to Azure.
9 hours ago
It's notable that they blame "our upstream provider" when it's quite literally the same company. I can't imagine GitHub engineers are very happy about the forced migration to Azure.
Having worked there around 2020-2021 there were many folks not happy with being forced to use azure and being forced to build GitHub actions based on azure devops. Lots of AWS usage still existed at that time but these days u bet it’s mostly gone.
I would imagine the majority of Github engineers there currently joined post MS acquisition.
That doesn't necessarily mean they're happy about Azure as a backend.
I've been a software "engineer" for over 20 years, and my personal experience is that software engineers are basically never happy.
4 replies →
> notable that they blame "our upstream provider" when it's quite literally the same company
As in why don't they mention Azure by name?
Or as in there shouldn't be isolated silos?
something about antifreeze in the dogfood