anthony taguest·sydney --:--
← hubnotes
> notes --tag engineering
Short notes I keep coming back to — mostly what I've learned building.
a library nothing leavesIf I ate it once I’ll eat it again — so nothing gets deleted, and the order has to come from somewhere other than me.engineeringAug 17, 2026test the habit before you build the toolThe storage was a solved pattern; the risk was whether I’d type six entries a day for a month. So I tried the typing first, with no tool at all.engineeringAug 16, 2026put the rescue before the overwriteFour writes, four crash points — the order you write them in is the recovery story you chose.engineeringJul 30, 2026retry before you write the root cause downA confident diagnosis confirmed by a confounded fix is still a guess.engineeringJul 24, 2026when my test suite showed up in my analyticsA test that hits a public recorder is a write — local runs must be forced secretless.engineeringJul 14, 2026absent and error are different nothingsWhen absence triggers setup, a flaky read must never look like an empty store.engineeringJul 12, 2026graceful degradation is an invariant, not a vibeA fallback only counts if the try starts at the first fallible line.engineeringJul 4, 2026the happy path hides the hardest inputA Japanese-input app shipped an Enter-to-send that broke for anyone typing Japanese.engineeringJul 4, 2026save the work, then mark it doneA blip on a cosmetic stats call threw away 38 paid AI judgments — a side-effect ordering bug.engineeringJun 25, 2026deterministic state machines pay for themselvesMake the core pure and the features you haven’t thought of get easier.engineeringJun 11, 2026
the hub · warm terminal