Feature flags are debt with an expiration date you must actually enforce. Tests are documentation that fails loudly when it goes stale. The rollback plan should exist before the rollout plan is approved.
Details
Naming things well saved us more time than any framework migration. Small pull requests get real reviews, large ones get approvals. We wrote the migration twice: once to learn, once to ship.
We wrote the migration twice: once to learn, once to ship. A boring deploy pipeline is a feature, not a lack of ambition.
Context
The best architecture diagram is the one the new hire can redraw from memory. Our on-call rotation improved the day we deleted half of the alerts. If the error message does not say what to do next, it is half an error message.
- Keep migrations reversible
- Measure p95 and p99, not just the mean
- Pin versions, update on purpose
- Delete dead code the same week
The fastest query is the one you never send, but the second fastest has a good index. Feature flags are debt with an expiration date you must actually enforce.
What worked
If the error message does not say what to do next, it is half an error message. Feature flags are debt with an expiration date you must actually enforce. We measured first, and the bottleneck was not where anyone expected. Most production incidents start as a small assumption nobody wrote down.
We wrote the migration twice: once to learn, once to ship. Small pull requests get real reviews, large ones get approvals.
The fastest query is the one you never send, but the second fastest has a good index. We measured first, and the bottleneck was not where anyone expected.
Leave a Reply