2026-07-15
Speed is a feature
If your pipeline takes 25 minutes, engineers batch changes and every merge becomes risky. Keep the critical path under ten minutes: parallelize tests, cache dependencies aggressively, and run the long tail (heavy integration tests, security scans) asynchronously after merge.
Make rollback the default path
Blue-green or rolling deployments with health checks mean a bad release is reverted in one action, not one afternoon. Combine with feature flags so incomplete work ships dark. The goal isn't zero bad deploys — that's unattainable — it's bad deploys that nobody outside the team notices.
Migrations are the real danger zone
Most rollback failures are database rollbacks. Adopt the expand-contract pattern: add the new column, dual-write, backfill, switch reads, then remove the old path in a later release. Every step is independently deployable and reversible.