← Back to context

Comment by Madmallard

6 hours ago

Why are they even changing GitHub?

Like what is the deal here? Why is the company ruining this program? Surely there can't be a financially sensible reason?

They've been moving it to Azure, presumably partly because they don't want to pay AWS for a thing they could (apparently) do, but more for the appearance of the thing.

I think that's financially sensible in the long run, assuming they believe they can run the thing basically as well on Azure, and aren't expecting major issues during the migration. These have turned out not to be good assumptions.

Because of vibe coding everyone is a developer now so the number of accounts, PRs, repos, etc just 10x'd.

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.

And that's just inexcusable.