So "X" - nothing to see here. Elon's in control - Part XXX **Threadbans in OP**

Well, that's what you get.

So I'm guessing what happened: IT dinosaur Musk decided to micromanage the Twitter tech stack, decided he'd play CTO. Probably demanded an audit of all the services running, took out a red marker and ordered the Devs to turn off stuff he didn't understand - or nobody remains around to explain what they did.

I'd not mind but I doubt switching off individual MicroServices had any quantative effect on the bottom line.

I'd laugh only the idea of Twitter going further down the shítter is great for humanity. As to Musk, to invoke the wisdom of the crowd:

I presume this will be fixed and they'll switch the 2FA services back on, among all the other aspects of Twitter that just broke. Surely Musk isn't such a fool to at least revert his rash decisions? Oh god, no. He'll probably just get the developers to duct-tape the dead services into the remaining live ones - Sunk Cost n' all that.

This is why we have a CTO folks, and they tend to operate with autonomy. And why Helicopter Management is not a good thing, no matter how many kazillions the boss made with electric cars.

Not assuming anything; but "incompetence" is a needlessly hostile accusation to put at the feet of the developers, when many of these scenarios are complex and not remotely black & white. Self-analysis is the hardest of all, and it can be difficult to find the time or headspace to step back from an existing pipeline and re-assess one's own structure. Much easier in SMEs than corporations for sure.

The developers' arguments to Musk seem like perfectly reasonable explanations why the app remains a problem - but Musk's response, and demonstrated management style thus, don't give any indication that there'll be an attempt to arrest this culture, be it accidental or deliberate.

I don't entirely disagree with you - but it can come down to culture. And, for that matter, something as simple as who's still there after those 10 years. Easy to say "...call it out early", but what do you do when the original architects from tech to management have moved on and a bunch of developers inherit a PoS codebase? Depending on the culture it could be next to impossible for even the gutsiest new developer to put their oar in and say "we need to stop adding stuff and fix this app".

I've been there and just with a recent US corporation I worked for, can think of a couple of internal tools that fit that bill. Absolute atrocious pieces of shít apps but for a host of reasons "fixing" them was next to impossible. Not least because those with the largest hats in the company had the "it works, doesn't it?" and that kinda ended those conversations.

Mind you. Getting into a spat with Musk was the wrong move by those developers - and may cost them in any future interviews if they now get a reputation as the type to air their dirty laundry in public. Equally though, I can see why a disgruntled developer might have had enough of Musk waving his díck about in public and barking about things he doesn't know or understand. That in of itself might charm other companies. As I said, Musk shouldn't be doing the CTO's job, and doing it so badly. TRying to shame Twitter's tech department isn't going to instil loyalty or enthusiasm