Dave Farley (author of the "Continuous Delivery", and "Modern Software Engineering" books) highlights in this video four questions that ought to have mitigated the impact of this failed update, or rather, ought to help mitigate similar incidents in the future:
1. Why wasn't this caught by Testing?
2. Why didn't they use Canary Releasing?
3. Why didn't CrowdStrike have proper Observability of this as it happened?
Dave Farley (author of the "Continuous Delivery", and "Modern Software Engineering" books) highlights in this video four questions that ought to have mitigated the impact of this failed update, or rather, ought to help mitigate similar incidents in the future:
Gregory's Server
@knightlie @marcan
Dave Farley (author of the "Continuous Delivery", and "Modern Software Engineering" books) highlights in this video four questions that ought to have mitigated the impact of this failed update, or rather, ought to help mitigate similar incidents in the future:
1. Why wasn't this caught by Testing?
2. Why didn't they use Canary Releasing?
3. Why didn't CrowdStrike have proper Observability of this as it happened?
4. Why no Rollback planned within the change?
https://youtu.be/MwjQVAwIATE?feature=shared
@knightlie @marcan
Dave Farley (author of the "Continuous Delivery", and "Modern Software Engineering" books) highlights in this video four questions that ought to have mitigated the impact of this failed update, or rather, ought to help mitigate similar incidents in the future:
1. Why wasn't this caught by Testing?