The migration that never finished
Half-completed migrations are the most expensive state a system can be in, and the most common one.
tech, developers, and the code underneath
40 pieces tagged opinion,
from January 3, 2025 to September 21, 2026.
Half-completed migrations are the most expensive state a system can be in, and the most common one.
Users cannot see your architecture. They can see the six seconds it takes to do the thing they came for.
The innovation-token argument is a decade old and still right, with one amendment nobody makes.
A checklist for the moment before you create a new deployable, when saying no is still free.
What writing in public taught me about engineering, what I was most wrong about, and why the archive is the point.
Every line you remove is one that cannot break, cannot be misread, and does not need to be maintained.
Portability is not free and neither is dependence. A framework for deciding how much abstraction to buy.
Write once, run anywhere, debug everywhere. The honest accounting of what each approach actually costs.
The role is genuinely ambiguous and that ambiguity is load-bearing. An attempt at a concrete description.
The received wisdom is never rewrite. The received wisdom is mostly right and has three real exceptions.
Running code close to users is a real win for a narrow set of workloads and a complication for everything else.
Internal platforms fail for predictable reasons. The successful ones share four properties.