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.
A gate that asks whether a result is bigger than nothing is asking the wrong question when the result was chosen as the largest of many. The maximum of a set of random draws is not zero and is not small: it sits predictably some distance…
The platform reports, about each account it holds, whether that account is live. The programme had been treating the flag as a fact about the world. It is not: one of the accounts it was pointed at was the rehearsal environment with the…
Two failures landed in the same pass, and they were the same failure twice. A guard meant to permit one open item per member never blocked anything, because the member identifier was derived from a text label by stripping a prefix and the…
A live path had placed nothing since it started, and the question was not whether it was broken but whether silence was still a legitimate answer. Two explanations fit the same observation: the conditions had not occurred, or they had…
A pass that was ready to act on its decisions was given a hold it could not talk itself out of. Until a per-account setting carries an explicitly signed value, every pass skips its actions and writes a hold record instead. The value does…
A live pass depends on a reference input produced outside the system, arriving on somebody else's schedule. That dependency is the classic availability-versus-legitimacy trade: when the feed is late, the system can act on what it already…
An operator-facing specification listed a set of operating windows as fixed wall-clock spans, described as holding all year. An auditor checked the table against the engine's own per-region calendars rather than against the previous version…
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…
Every risk document has a worst-case line, and that line is usually taken at face value. One candidate's single worst day was an extreme outlier, far outside everything around it. It would have been easy either to discard it as noise or to…
Two candidates were put through the full gate set. Each had satisfied a progression condition that had been set as a required precondition, and satisfaction of that condition was widely expected to be the deciding factor. Both were rejected…
A campaign sweeps a large grid of configurations and ranks them on a computed score. Near the top of the grid, the score stops being informative, because the quantity being scored is bounded — a proportion cannot exceed one — and any design…
A candidate had been admitted into a collection on the strength of a strong measured result. Later, an unrelated defect fix changed how one component of that measurement was computed. Re-measured, the candidate did not merely weaken: the…
A large sweep produced a map of candidate configurations, and the map was produced once, on one machine, by one program. That is exactly the situation in which a subtle dependency on the machine — an ordering, a threading choice, a…
Before a decision stream is allowed to feed anything live, it has to pass a registration gate. The interesting part is not that the gate checks the output is well formed. It is that the gate tries to show the output could have been produced…
An archive had stopped at a fixed date, and a study needed it to continue past that date. The dangerous move is the obvious one: rebuild the whole series from new inputs and accept whatever comes out, because then every earlier result…
A quality filter had been in place since the archive was assembled, and it was simple: keep a value only if it does not differ from the last value kept by more than a declared bound. That filter carries an assumption nobody had written down…
A family of published results had been computed on a cost basis assumed to be the right one. A check of what was actually on disk showed otherwise: the cost surface underneath came from a third-party historical source that covered only a…
An independent reviewer was asked a deliberately unfriendly question about the decision log: not whether it recorded the right outcomes, but whether a reader could tell from the record alone why nothing happened at a given moment. The…
Restarts are where a live system loses its argument with itself. Nothing crashes; the process returns, reads its configuration, and begins the day fresh — except that the day did not begin when the process did.
A condition can be written two ways that are equivalent for every number and behave differently for the value that is not a number. The reference implementation asked whether the magnitude of a statistic had reached a threshold, written…
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.