Sixteen projects, counted rather than claimed.

I build things end to end — the Postgres schema, the service in front of it, the interface people touch, and the pipeline that puts all three somewhere reachable. Then I keep going until it runs somewhere other than my laptop.

The catalogue here is an audit, not a highlight reel. Each entry carries what the code actually contains: the real stack from its dependency manifest, its commit count and date range, whether it has tests, and whether it is deployed. Where a project is half-finished it says so, and where a README overclaimed I wrote down what the code does instead.

This site is one of the entries. The catalogue lives in Supabase, a Go API serves it, and the assistant in the corner answers from that same database rather than from a script — so it can only tell you things that are true of the work on this page.

Where the tests are

Most of these projects have no automated tests, and pretending otherwise would be the easiest lie on the page. Four do, and those are the ones worth naming:

The two suites marked passing were re-run while writing this, not read off an old badge. Everything else was verified by exercising the deployment directly.