The hard part was never the code
I have rebuilt the same platform more times than I would like to admit — migrations gone sideways, a server deleted in an instant taking months of infrastructure with it — and each time the code came back faster than the last. The code was never the bottleneck. Clarity was: knowing what to rebuild and, more importantly, what to leave behind. The lessons that survive every rewrite are never technical — forensic honesty beats optimism, patch before you rebuild, and the system that scales is the one that never needs you in the room. I have lost a lot of code. I have never lost those.
I have rebuilt the same platform more times than I would like to admit. Migrations that went sideways. A server deleted in an instant, taking months of infrastructure with it. Each time, the code came back faster than the last. The code was never the bottleneck.
The bottleneck was clarity — knowing what to rebuild and, more importantly, what to leave behind. A rewrite is a rare gift: a chance to not carry forward the mistakes you have grown too used to notice.
A rewrite is not a do-over. It is a chance to be honest about what mattered.From the essay
The lessons that survive every rebuild are never technical. They are things like: forensic honesty beats optimism, patch before you rebuild, and the system that scales is the one that never needs you in the room. I lost a lot of code over the years. I have never lost those.