What I’m more surprised about is how gum and shoestring the twitter engineering is now a days. They put in no emphasis on doing deep divides into the code base and instead opt to do the simplest shortest fix. And it causes problems.
Instead of engineering trying to buffer and fix weird management decisions, this just exposes them.
Elon strikes me as worse because he likes to think he understands what his engineers know.
What I wanted to say is that if the state of the code is bad, it might make them care a bit more when their own state gets synchronized with that. Not necessarily about the code, but surely about the revenue and the looks.
Now, management being what it is, they of course will try to find a scapegoat. But that’s just part of the game and may be better than burning yourself out by trying to fix their nonsense.