A small tool for big diffs

I used to add a layer of abstraction the first time I saw a pattern repeat. Now I wait for the third. The waiting is uncomfortable, but the abstractions that survive that wait tend to last.

Every time I revisit a project after six months, I find at least one place where past-me wrote a comment that present-me has now stopped trusting. Comments rot faster than code.

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.

The team I learned the most from didn't have great tools. They had a great habit of reading each other's pull requests in full, including the parts that weren't theirs.

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

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.