The rollback plan should exist before the rollout plan is approved. The fastest query is the one you never send, but the second fastest has a good index. A boring deploy pipeline is a feature, not a lack of ambition.
A small example
Latency percentiles tell a story that averages politely hide. Security is mostly about saying no to defaults that were convenient in 2010. We wrote the migration twice: once to learn, once to ship.
If the error message does not say what to do next, it is half an error message. Tests are documentation that fails loudly when it goes stale.
What didn’t
The rollback plan should exist before the rollout plan is approved. We measured first, and the bottleneck was not where anyone expected. A boring deploy pipeline is a feature, not a lack of ambition. Security is mostly about saying no to defaults that were convenient in 2010.
- Write the failure mode down before writing code
- Delete dead code the same week
- Pin versions, update on purpose
- Keep migrations reversible
Tests are documentation that fails loudly when it goes stale. Every retry needs a budget, otherwise it is just a slower outage.
Context
Security is mostly about saying no to defaults that were convenient in 2010. We measured first, and the bottleneck was not where anyone expected. The fastest query is the one you never send, but the second fastest has a good index. The rollback plan should exist before the rollout plan is approved.
We wrote the migration twice: once to learn, once to ship. Small pull requests get real reviews, large ones get approvals.
We measured first, and the bottleneck was not where anyone expected. We wrote the migration twice: once to learn, once to ship.
Leave a Reply