zlacker

[return to "Twitter Is DDOSing Itself"]
1. andrey+Oh1[view] [source] 2023-07-02 04:20:31
>>ZacnyL+(OP)
> Twitter is firing off about 10 requests a second to itself to try and fetch content that never arrives because Elon's latest genius innovation is to block people from being able to read Twitter without logging in

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.

◧◩
2. willia+4j1[view] [source] 2023-07-02 04:38:09
>>andrey+Oh1
> why is he being attacked for a bad deployment?

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).

◧◩◪
3. andrey+xj1[view] [source] 2023-07-02 04:43:39
>>willia+4j1
Should a CTO perform UAT?
◧◩◪◨
4. willia+hk1[view] [source] 2023-07-02 04:52:46
>>andrey+xj1
A CTO is responsible for failures in the technology org. A CTO who describes himself as responsible for "sysops" is specifically responsible for failures in SRE/ops. Leaders are responsible for work they didn't personally do. If they don't want to be responsible for their reports then they can always go back to being a junior IC.
[go to top]