zlacker

[return to "Twitter Is DDOSing Itself"]
1. Topfi+Ew[view] [source] 2023-07-01 21:09:47
>>ZacnyL+(OP)
Speaking from very painful, personal experience, few things are more agitating than being forced to execute on something you fully know is a horrible idea, especially when you tried and failed to communicate this fact to the individual pushing you to go against your best judgement.

Even more so when that person later loudly proclaims that they never made such a request, even when provided with written proof.

I can of course not say whether the people currently working at Twitter did warn that the recent measures could have such major side effects, but I would not be surprised in the slightest, considering their leadership's mode of operation.

Even as someone who very much detests what Twitter has become over the last few months and in fact did not like Twitter before the acquisition, partly due to short format making nuance impossible, but mostly for the effect Tweets easy embeddability had on reporting (3 Tweets from random people should not serve as the main basis for an article in my opinion), I must say, I feel very sorry for the people forced to work at that company under that management.

◧◩
2. praise+TL[view] [source] 2023-07-01 22:59:23
>>Topfi+Ew
>Speaking from very painful, personal experience, few things are more agitating than being forced to execute on something you fully know is a horrible idea, especially when you tried and failed to communicate this fact to the individual pushing you to go against your best judgement.

In this case the horrible idea is being forced to push changes to production at a moments notice

◧◩◪
3. Topfi+Yy1[view] [source] 2023-07-02 07:44:14
>>praise+TL
Yes, that is very much true. Even if, as some have commented, the people remaining at Twitter lack oversight over the entire codebase to predict that this specific change could have such a knock-on effect, not having testing and staging environments, pushing something straight to production, would give even an inexperienced person pause for thought.

As said, I don't want to speculate whether someone raised their voice on this being a likely outcome specifically, as not having testing prior to release is the much more obvious and significant issue here, driven by leadership.

[go to top]