Writing Migrations You Can Roll Back
A migration without a tested down path is a one-way door. We treat reversibility as a requirement, not a nicety.
Archive
Page 2
A migration without a tested down path is a one-way door. We treat reversibility as a requirement, not a nicety.
Rolling deploys, health checks that actually check health, and the database migration rule that saved us.
Stringly-typed flags are a footgun. A tiny bit of TypeScript turns typos into compile errors.
Every new technology spends innovation tokens. We spend ours deliberately, and keep the rest of the stack delightfully boring.
RSS climbed 40MB an hour until the pod OOM'd. A heap snapshot and one closure later, we found it.
Three changes — a moment.js eviction, route-level code splitting, and tree-shaking a barrel file — cut 60% off our JS.