How this site runs
This website is the smallest production system I operate, and it's run like one: shipped from a pipeline, traceable to a commit, and measured honestly. Consider this page its runbook.
## The build serving you this page
## Your session, measured live
Measured in your browser, on this visit — not a screenshot of a good day. Thresholds follow the Core Web Vitals definitions.
## The stack
## Decisions worth flagging
Numbers are measured or absent
Every metric on this site — build SHA, load time, the vitals below — is measured at build or in your browser. If something can't be measured honestly, it isn't shown. A portfolio that sells observability shouldn't fake its own telemetry.
The deploy is traceable
The footer shows the exact commit serving you this page, linked to the repository. Every deploy is a commit; every rollback is a revert. The same discipline I set up for client platforms, applied to a website.
No cookies, no tracking pixels
Analytics is Plausible — aggregate, cookie-free, no consent banner needed. The Content-Security-Policy is strict enough that a stray third-party script simply won't load.
Fonts are self-hosted
JetBrains Mono and Inter ship from this domain via next/font. No requests leave for Google Fonts; the CSP wouldn't allow them anyway.
The hero is a canvas, not a video
The glyph field on the homepage is ~150 lines of hand-written canvas: two interference waves over a stable character grid, redrawn on a 15fps budget, paused when offscreen, and reduced to a single static frame if you prefer reduced motion. No WebGL library, no shader bundle, no autoplaying video.
Dark only, on purpose
One audience, one context: engineers, usually at a desk. Maintaining a second theme would double the design surface for a mode almost nobody here would choose.