Comment by usrnm
1 day ago
How is the fact that it was a database change and not a binary or a config supposed to make it ok? A change is a change, global changes that go everywhere at once are a recipe for disaster, it doesn't matter what kind of changes we're talking about. This is a second Crowdsrike
This is the core point. A canary deployment that was not preceded by deploying data that activates the region of the binary in question will prove nothing useful at all, while promoting a false sense of security.
The root problem is that a dev team didn't appropriately communicate criteria for testing their new feature.
Which definitely seems like shortcut 'on to the next thing and ignore QA due diligence.'
Google does not separate dev and QA in general (I'm sure there are exceptions).
1 reply →