[zadokshi]

This article can be rewritten into one line:

“Not all bugs can be found until you deploy to production. So deploying to production can be called ‘testing in production’”

[K0balt]

The (somewhat obvious) parts about staged rollouts and selection criteria for initial deployments are useful. If CrowdStrike had rolled to a small demographic first. Billions of dollars could have been spared the shredder.

[hot_gril]

Sometimes it's not so simple. If your prod is already broken, a slow rollout becomes a liability. CrowdStrike didn't have any real reason for a global push, but if it were to patch a 0-day already being exploited, customers might rather risk downtime than breaches.

[AmericanChopper]

Eventually you’re going to make a change that completes 100% of the production rollout. That change should be tested too, as any change is a new opportunity to break something.

[boesboes]

I bet staged rollout are on some poor PO's backlog. We don't have the bandwidth for such niceties! :')

[fragmede]

Everyone has a test environment, the lucky ones have a separate production environment.

[djtango]

I thought the colour and anecdotes were useful towards conveying the message. Sometimes only after you've experienced something for yourself does the reduced pithy one liner make sense and resonate.