Well, for one, this sounds just like yet another Elon-hater's comment. In _most_ cases, Elon's businesses are fairly successful, so a sarcastic "Elon's latest genius innovation" doesn't belong here.
For second, how do you know the idea came directly from Elon? It could easily be the result of a brainstorming session led by a product team.
Elon is not writing Twitter's code. He is not a Software Engineer at Twitter. Even if the idea came from him, why is he being attacked for a bad deployment?
And lastly, why do people think that the change is bad? There are plenty of web sites that do not allow you to view their content without creating an account first. Is Twitter not allowed to experiment? Why not? I would appreciate hearing well-thought-out arguments that explain the potential negative impact on the business.
Edit: here is my take on it + the most likely scenario of what's going to happen next. This was a bad deployment and such things are not unusual in software industry. In this specific case, there are zero reasons to blame the CTO. From what I'm observing right now, Twitter has already fixed the issue - the website loads just fine. Next, they will do a retro, learn from their mistakes and try to not repeat the same mistakes again in the future. There will be more bad deployments and that's normal. However, with time, they'll make things better, the SLA will go up and the overall stability of their services will stabilize, – one of the biggest social networks on the planet will have the least number of engineers running that same social network.
Because it's quite literally one of the things he's responsible for at Twitter, by his own choice and description of his role (https://twitter.com/elonmusk/status/1656748197308674048).
The point of a decision-maker is to make informed decisions, if you fail to do that, then you fail at leadership.
(B) Are you familiar with the expression “the buck stops here”?
it's a 429 error, so the developer who posted this is an idiot. they're not even wrong. the 429 doesn't even touch twitter's infrastructure
https://blog.twitter.com/engineering/en_us/topics/infrastruc...
it's a 429 error, so the developer who posted this is an idiot. they're not even wrong. the 429 doesn't even touch twitter's infrastructure. the HTTPS TLS terminates at a Google VM, which gets relayed depending on the VIP used to hit it, but the traffic never gets past that Google VM. This is literally /HOW/ companies deal with DDOS.
https://blog.twitter.com/engineering/en_us/topics/infrastruc...
it's unbelievable that my median salary for the past decade is $3,000 after several years of "Startup" followed by "How to Start a Reboot of My Life"