field notes
Short notes from real engineering work: one decision, one incident, one reversal at a time. Each one names the shape of the problem, the tension that made it hard, the decision, and what it cost. The internals stay out — the codename is the hint.
If you have five minutes rather than an afternoon: the three case studies condense this material to one problem, one decision and what the decision cost. The notes below are the record those studies cite — and the projects the codenames belong to are on the front page.
The periodic summaries in this record are numbered. The numbers do not run consecutively. Inside a working stretch where the neighbouring numbers are all present, several are simply missing, and nothing in the record explains the absence or…
A report named the peak of a long excursion: a specific date, with the worst excursion-from-peak measured against it. A later reader noticed the date could not be right. The named peak came after the trough it was supposed to belong to. A…
method
Not a changelog entry and not a repository summary. One decision, one incident, one reversal, or one hard-won invariant — the thing an engineer would tell you at a whiteboard.
Prefer records with dates and root causes? Those are on incidents. Live numbers are on stats.