YOLO Is a Terrible Strategy for Validating Production Changes
Explores why YOLO is a bad strategy for validating production changes and offers better methods like canary releases, shadow traffic, and smoke tests.
Explores why YOLO is a bad strategy for validating production changes and offers better methods like canary releases, shadow traffic, and smoke tests.
Compares Canary and Blue/Green deployment strategies, explaining their complexities, use cases, and when each is optimal for software releases.
Explains how a microservices architecture is essential for successful blue/green deployments and common pitfalls when services are not independent.
Analyzes how cognitive biases like prevention bias and status-quo bias lead to inefficient software deployment practices like 'No Friday Deploys'.