Writing
Write-ups from production.
Case studies, a re-runnable benchmark, and field notes from real systems under real load. Every claim in them traces to something you can check: public data, a public repo, or a decision written down when it was made.
Where a demo ends and production begins.
A demo proves an idea works once. Production is where it has to survive real cost, real failure, and real load. The three places software breaks when real users arrive, and how to engineer against each, with the measured proof behind every claim.
Read itA self-hosted model matched cloud quality at a tenth of the latency.
A reproducible benchmark. 1,200 vision-analysis calls across six backend arms, three cloud models, one also run with extended thinking off as a control, and two self-hosted, on the same scenes with two blind judges. A self-hosted 30B model matched the best cloud model's quality within statistical noise while answering in 0.77s, five to ten times faster, at no per-call cost. Raw data and the runner are in the repo.
Read itA one-page concept, taken to a multi-region game-hosting platform.
A case study. Over a six-month engagement I led the design and build of MetricHost, a multi-region game-server hosting platform, from a one-page concept to production. k3s, Cilium eBPF, a Go control plane, idle-server hibernation, and the honest cost call that ended it.
Read itWhen a vendor moves the floor overnight
When a single hosting vendor repriced its machines overnight, it broke the assumption a whole business was built on. A write-up on doing honest unit economics: verifying per-GB-RAM cost at the source, building a portable multi-vendor mix, separating RAM efficiency from instance price, and telling a client the real number.
Read it
If one of these sounds like the problem on your desk, describe it to me. You get a straight answer about where I'd start, and asking costs nothing.
Tell me what's breaking