A short list of useful Make targets
Ines · Dec 19
I keep a small log of decisions in a text file. Not architectural — just small ones. "Picked X over Y because Z." Future me reads it more than I thought he would.
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.
I trust monorepos more in the second year than I did in the first. Most of the early friction goes away once the tooling catches up.
Caches solve a problem and create three new ones: invalidation, observability, and the slow drift between what the cache thinks is true and what the source thinks is true.
← back to index