Months of static analysis, two real bugs

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.

Most retry logic I've removed turned out to be hiding a real bug. The retries made the failure invisible, and the bug compounded for months in the background.

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.

If a config file has more than a dozen options, half of them aren't being used. The other half are being used in ways the original author didn't predict.

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.

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