field notes

Writing

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.

source notes/ · 252 notes · 10 codenames · newest first · atom feed

All field notes

filter by theme · 244 total

the object that would not move

A new research line looked unusually good on paper. Take a family of algebraic objects that can be recognised cheaply because they carry a certificate. Let a hidden group action walk over a congruence level of that family. Read a shared…

read

the verifier that was too large to run

The check suite for one research result had grown in two directions at once, and the two copies had stopped being interchangeable. One enumerated a few dozen properties and exercised them end to end. The other, written later by a different…

read

two agreeing points are not a derivation

Between two representations of the same algebraic object there is a conversion, and ours had been calibrated rather than derived. Two corresponding points had been measured by hand, and the conversion was fitted through them. It reproduced…

read

method

What a field note is

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.

shape
What made the problem genuinely hard, before any solution appeared.
tension
The two things that could not both be true — stated precisely, because that is the part that transfers.
decision
What was chosen, and what it cost. Cost is the credibility; a decision with no cost attached has not been described.
ceiling
A codename, a theme, and a class of problem — never a hostname, a parameter, a version or a vendor. Under the disclosure rules the hint is the category, not the instance.

Prefer records with dates and root causes? Those are on incidents. Live numbers are on stats.