// writing · 05 entries
Build logs, not blog posts.
Long-form notes on things I actually built: what the problem was, what I decided, and where the decision turned out to be wrong. No hot takes, no listicles.
SERIES · building-openinvarA correct answer nobody acts ongraphyn answered "what breaks if I change this" correctly for months, and almost nobody changed what they did with the answer. Renaming it to OpenInvar meant admitting that an advisory tool and a gate are different products — and that determinism stops being a preference the moment a tool is allowed to say no.agentscideveloper-toolsmcpopeninvarruststatic-analysisMIN READREAD →SERIES · building-audio-relayThe audio was on time. It just arrived all at once.Shipping audio-relay meant learning that a real-time pipeline is judged by its tail, not its average. The throughput was correct the whole time it was unlistenable — here is the 341ms stall that caused it, and the two other bugs that were the same bug wearing different clothes.audioaudio-relaykotlinnetworkingreal-timerustMIN READREAD →SERIES · building-openinvarWhat breaks if I change this?Grep answers a question nobody asked. Building OpenInvar meant deciding what a relationship between two symbols actually is — and living with that definition across a dozen languages.developer-toolsgraphsmcpopeninvarruststatic-analysistree-sitterMIN READREAD →A Markdown renderer is a browser you didn't mean to writeTurning Markdown into a PDF means measuring text, breaking lines, paginating, and — the part I did not plan for — fetching arbitrary URLs on behalf of untrusted input.layoutopen-sourcepdfrenderingsecuritytypescriptMIN READREAD →SERIES · building-quantajsReactivity is easy until someone calls .clear()Building QuantaJS taught me that a reactive system is defined by its worst case, not its demo. Here is the whole dependency engine, and the collection bug that took the longest to admit was a design flaw.open-sourceproxyquantajsreactivitystate-managementtypescriptMIN READREAD →
index · RSS and Atom generated from the same frontmatter · drafts render in dev and never ship
// case studies
The long version of 5 of them.
Each build log has a case study behind it: the shape of the system, the tables, and the limits stated out loud.