zlacker

>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

>>praise+(OP)
> push changes to production at a moments notice

Isn't that one of the DORA metrics?

>>tbrown+58
Yes, but so is Change Failure Rate (and a good team will use feature flagging anyway for gradual rollouts, so you don't roll out a DDoSing broken feature to 100% of users, just a tiny subset).

>>praise+(OP)
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.