About
Why this exists
Most software writing begins after the interesting parts have been sanded off.
The interface is polished. The diagram is symmetrical. The failure mode is described as “an edge case,” which is a charming way to say nobody planned for it.
Systems / Signals exists to document the machinery underneath: state transitions, ownership, trade-offs, failure modes, and the small experiments that reveal whether an idea survives contact with reality.
The subjects include AI engineering, agent architectures, LLM infrastructure, distributed systems, software architecture, and developer tooling. In other words: systems that become interesting precisely when they stop behaving like diagrams.
How it is made
Articles are written in Quarto Markdown and published as static HTML through GitHub Pages.
Code, diagrams, equations, citations, and comments live close to the argument they support. There is no custom backend, no database, and no mysterious service quietly accumulating operational debt. The system is intentionally boring. That is the point.