One commit, two months of cleanup

I split a 4000-line file into 12 smaller ones this week. The smaller files weren't actually easier to understand. The 4000-line file was a problem of structure, not of length.

There's a kind of premature optimization that comes from imagining a future team. "What if someone needs to swap this out?" Often, no one does.

Latency budgets work better than latency targets. Targets are aspirational. Budgets force you to delete features when you go over.

Most of the trouble I see in production comes from boundary cases someone promised would never happen. The code is fine. The plan is fine. The promise is what ages badly.

The fastest debugging trick I've learned is to write out, in one sentence, what the system is supposed to be doing. Half the time I notice the bug while writing the sentence.