One thing I hate about GH's status page: sure "auth" gets to live under API, so API gets the downtime report today. But all of my remote git ops are failing, because i was dumb enough to use the `gh` cli to auth. Their status pages are not well defined, but they treat them as such, leading to inflated uptime numbers.
There is ALWAYS a need to scale up, upgrade versions, migrate from one database or scheme to another, cut services into more microservices, melt them back into a monolith, integrate more stuff, deprecate other stuff, fix bugs, increase performance, tune caches…
Some things happen for reasons that make sense, others are done for the sake of it. The PO‘s of front end features need to evolve them. What do you do with a PO who says this is done? They don‘t have visibility, don’t get promoted and they don‘t get a bonus. We have created a dashboard that shows that A/B tested users like the new design more by 7%! The next redesign is already planned!
Line must go up. They're already the default choice for hosting software repos online, so it's time to look at the next thing, whether that be CI/CD or AI or whatever.
If line doesn't go up, some Ivy League business school grad who has holdings in MS might make slightly less money and have to cut back on the nose candy budget while summering in the south of France this year.
To a certain extend I can fully accept that GH has scaling issues because of the insane traffic increase from AI generated code. But they are owned by one of the largest technology companies in the world, who also happens to run a hyperscaler.. so..