01
Latency is an ownership problem
Voice-agent latency is a chain of accountable decisions—not a flattering average on a dashboard.
::02 /var/lib/knowledge/index
Field notes from the machinery.
Technical records preserve decisions, expose failure modes, and leave behind something sharper than a retrospective. Press / or ⌘/ to search; Esc clears the field.
/
21/21 records
02
Memory without provenance is a liability
Embeddings must not erase source, trust, sensitivity, permission, expiry, or the right to say no.
03
Your program can fail before main
A compact C++ failure mode: global initialization crosses translation units, and startup becomes link-order roulette.
04
Memory is a lifetime contract
Stack or heap is not a trivia question. It is a promise about ownership, lifetime, movement, and cleanup.
05
UWB is easy. Field calibration is not.
The radio can measure distance. The product still has to survive geometry, calibration, provisioning, clocks, enclosures, and the field.
06
Cryptography begins with the threat model
Before choosing a primitive, put the adversary, asset, channel, and exact cost of failure on the table.
07
Fibonacci coding: compact by construction
A small algorithm file on universal integer coding, representation choices, and the value of keeping primitives testable.
08
Tools are part of the operating system
Editors, shells, agents, and automation are not accessories. They are the control plane for how engineering work is understood and shipped.
09
An agent interface needs an abort button
Autonomy without state, approvals, interruption, and recovery is not power. It is a process that cannot be trusted.
10
Async cancellation is a protocol, not an exception
A streamed agent cannot recover cleanly if cancellation is merely thrown into a task tree; interruption needs identity, propagation, acknowledgement, fencing, and an observable terminal state.
11
Reliability in XDP is a state-budget problem
Implementing IEEE 802.1CB-style replication and elimination near the Linux receive path forces every guarantee through verifier constraints, bounded state, cache locality, and explicit sequence-window semantics.
12
A transcript flush is a distributed commit problem
Retries, reconnects, races, and shutdown turn “save the conversation” into an occurrence-identity problem: the database must know which logical event committed, not which transport attempt happened to arrive.
13
Inflation expectations are a feedback state
Expectations can transmit a price shock into later wage and price decisions, but “anchored” is an empirical property—not a slogan and not a forecast oracle.
14
Prediction error is a teaching signal, not pleasure
Temporal-difference error explains a precise pattern in dopamine-neuron responses, but the useful model is narrower than “dopamine equals reward.”
15
Signal detection separates sensitivity from willingness
Accuracy mixes perceptual sensitivity with decision criterion. Signal detection theory keeps the evidence distribution and the action threshold separate.
16
bpftrace is a microscope, not a dashboard
A handful of one-liners that answer "who is doing this syscall, on what file, right now" without touching the kernel module machinery.
17
A lighting engine is a state machine, not a remote control
Tying Hue, Govee, audio gear, and projectors into one coherent scene system means treating the living room as a publish-subscribe device graph with a recovery contract.
18
A DJ controller is the best home-automation remote
Physical faders, pads, and encoders beat a phone screen for lighting, media, and scenes. The bridge is a bidirectional MIDI-to-everything sync loop with state feedback.
19
Load models JIT, unload them immediately
A 32GB GPU is a shared resource. The discipline is not "which model to run" but "how to load, serve, and evict models so VRAM stays free for the next task."
20
A homelab is a small datacenter with a recovery contract
Proxmox, Caddy, NetBird, and Docker Compose on one box is enough to run a real infrastructure fabric. The discipline is treating the single node like a datacenter: backups, IaC, and tested recovery.
21
Attention needs admission control
Notifications, messages, and self-interruptions are competing producers. Deep work survives when admission, batching, breakpoints, and recovery become an explicit protocol.