Brutal.
-
Brutal.
When Microsoft acquired GitHub.
@ironicbadger big oof (for smallish values of oof) but I’d also like to see that graphed against active usage volume to get the full picture
(yes, regardless, a “hyperscaler” should be able to handle the volume)
-
Brutal.
When Microsoft acquired GitHub.
Why settle for Five Nines of reliability when you can get Nine Fives?
-
Brutal.
When Microsoft acquired GitHub.
@ironicbadger hmm, quite a few opinions on that chart
tl;dr it’s complicated.Most of GitHub services, until I left a couple of years ago were not on Azure.
-
Brutal.
When Microsoft acquired GitHub.
@ironicbadger Acquire and ruin. This is the corporate way.
-
Why settle for Five Nines of reliability when you can get Nine Fives?
@DaveMWilburn @ironicbadger get the sweet 55.5555555% availability
-
R relay@relay.mycrowd.ca shared this topic
-
@ironicbadger as a post msft acquisition survivor this tracks
-
Brutal.
When Microsoft acquired GitHub.
@ironicbadger Just like when they bought Hotmail back in the day.
-
Brutal.
When Microsoft acquired GitHub.
@ironicbadger Where was this chart published?
-
@ironicbadger hmm, quite a few opinions on that chart
tl;dr it’s complicated.Most of GitHub services, until I left a couple of years ago were not on Azure.
@andymckay @ironicbadger what's complicated about it? it used to be good and now it's bad
-
@ironicbadger Where was this chart published?
@a_different_jlh https://damrnelson.github.io/github-historical-uptime/
Sorry I should have linked to the source
-
@andymckay @ironicbadger what's complicated about it? it used to be good and now it's bad
@aburka @ironicbadger ah I was replying to a different post about it being Azure or Azure management. I did Mastodon wrong, sorry.
I will say after the acquisition when GitHub became rapidly more complex as features were added, the definition of downtime requiring a status change became a lot more strict and focused (for some teams). A bit more loose and easy beforehand.
-
@aburka @ironicbadger ah I was replying to a different post about it being Azure or Azure management. I did Mastodon wrong, sorry.
I will say after the acquisition when GitHub became rapidly more complex as features were added, the definition of downtime requiring a status change became a lot more strict and focused (for some teams). A bit more loose and easy beforehand.
@andymckay @ironicbadger yeah I can believe there are many causes, mismanagement and forced development speed as much as technology changes
-
Brutal.
When Microsoft acquired GitHub.
@ironicbadger behold the jagged teeth of the dog that eat all the dogfood!
-
Brutal.
When Microsoft acquired GitHub.
@ironicbadger Could anyone explain to me, how is this possible?
I would imagine they would keep things running on the original hardware etc. which I wouldn't expect to fluctuate like this. -
@Tubsta @ironicbadger iirc they were like halfway through rolling it out when Microsoft bought them lmao
-
@ironicbadger Could anyone explain to me, how is this possible?
I would imagine they would keep things running on the original hardware etc. which I wouldn't expect to fluctuate like this.@Jourei @ironicbadger Move fast and break things!
-
Brutal.
When Microsoft acquired GitHub.
@ironicbadger @isotopp what’s the data source behind it? Official status page? Because that has been notoriously inaccurate long before microslop took over.
-
@a_different_jlh https://damrnelson.github.io/github-historical-uptime/
Sorry I should have linked to the source
-
Brutal.
When Microsoft acquired GitHub.
@ironicbadger The inverse Midas touch
-
@DaveMWilburn @ironicbadger get the sweet 55.5555555% availability
@kaito02 @DaveMWilburn @ironicbadger works 50% of the time, all the time.
