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.
Early on in my career I had a name for this. I called it "gamle helter" in Norwegian which roughly translates to "old heroes". An "old hero" is someone who used to be competent in a field, has stopped being competent, doesn't recognize this themselves and is now a nuisance to anyone who actually knows what they are doing, but can't pull rank. One way to become an old hero is typically to end up in management and not practice whatever discipline you think you understand.
To be fair, I highly doubt that Musk was ever a competent software engineer, much less a good engineering manager. He is a PR person. He sells an image that he is a technology person.
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.
Since you linked Wikipedia, I'll quote it.
> Nevertheless, low performers' self-assessment is lower than that of high performers.
> Among laypeople, the Dunning–Kruger effect is often misunderstood as the claim that people with low intelligence are more confident in their knowledge and skills than people with high intelligence.