THE SYSTEM BEHIND THE SITE

How this site
is built.

A personal site should show judgment as well as tools.

Two applications, different jobs.

Astro serves the site and writing. EmDash manages content in D1, with media in R2. The separate engineering lab uses Solid 2, a Web Worker for simulation and a Hono API for saved scenarios.

The experimental boundary is explicit.

Solid 2 is pinned to a release candidate. It is confined to the lab, so the content application does not depend on experimental rendering behavior. React supports the EmDash editor; it is not shipped as a UI framework for the site.

Checked before every release.

The codebase includes a mathematical reference test, typed input validation, database migrations, browser acceptance tests and a gated deployment workflow. Runtime logs live in Workers observability. Data recovery is documented separately from code rollback.

Less is intentional.

The site and lab share a graphite-and-teal design system and a self-hosted Space Grotesk font. Editorial content renders as HTML. A small shared enhancement adds appearance preferences, a search shortcut and an explicit print action. The homepage adds a small, separately budgeted native-browser experiment, selecting prerendered infrastructure resilience states. Its initial comparison is prerendered. Cooling Lab offers a guided challenge and replay that respects reduced motion. No external font service is contacted.

Counting visits, not visitors.

The shared enhancement also sends one small, first-party request per page view, and one when the profile PDF is downloaded. It records the page, the referring site, the country and whether the device is a phone. No cookie, IP address, browser fingerprint or third-party script is involved, and browsers that send Global Privacy Control or Do Not Track are not counted.