This week's five picks

Five things worth your time, each with where it came from and why it made the list.

1. A calmer way to cache builds

Source: Build Notes, 2026-10-06. Why: it measures cold and warm builds on the same machine, and says what it could not measure.

The cache is only as good as its key.

2. Why tests flake

Source: Test Weekly, 2026-10-07. Why: a short taxonomy you can use in a code review.

• order dependence
• shared clocks
• unbounded retries

3. A parser that stays small

Source: Parser Digest, 2026-10-08. Why: the API is a page long, and the benchmark is reproducible.

4. Reading a postmortem

Source: Ops Journal, 2026-10-09. Why: it separates what happened from what was decided afterward.

1. read the timeline first
2. then the decisions
3. then the follow-ups

5. A note on defaults

Source: Defaults Quarterly, 2026-10-10. Why: a defaults list is a design document, and this one reads like one. Use --strict where you can.

That is the issue. Reply to this email with what you would like more of.