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 platform shipped its public surfaces before it shipped a limit on how often they could be asked. That is the ordinary order of events, and the review said so plainly: no request budget at all on the server facing the public. The fix…
The public marketplace needed to show, for every venue, a small card of near-live facts: a rating, a delivery fee, an arrival estimate. The obvious implementation is a query — the page asks the database whatever is true right now. The…
The useful property of a ranked defect inventory is that it can be re-read. The harder discipline is reading it again and writing down how little has changed, in the same order, with the same numbering, so the gap between what was claimed…
A multi-surface platform — a public marketplace, several venue sites, staff tools, an operator console — accumulated hundreds of commits before anyone read the whole thing with a hostile reader's patience. The review that followed was not 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.