Fleet Command
How a drawer full of mismatched PCs learned to behave like one AI service, and what broke on the way.
Some of these started as "how hard can it be?" and turned into months. Each write-up is the honest version: what I built, how it is put together, what went wrong, and what I would tell myself at the start. Pick one, or go and play something first. I won't tell.
Long reads with diagrams and a dashboard each. Every number comes from the project's own records, not from memory.
How a drawer full of mismatched PCs learned to behave like one AI service, and what broke on the way.
A tool that reads every project I have and tells me what is actually true about them, including the parts I would rather not hear.
A province's airborne laser survey, turned into a block world you can walk around in a browser.
Moving a Python kart racer into the browser without letting a single tick drift, and proving it.
The voxel engine underneath the racers, with the trailer and the film.
A game engine written from scratch in Python, and the vehicles it grew.
Things that run in your browser right now. No install, no sign-up.
Kart racing in the browser. Bring a keyboard, a pad or a thumb.
Orbit, fly or walk through a province built from laser survey data.
A trading voyage across old sea lanes. Buy low, sail far, try not to sink.
A small strategy game whose rules were written by hand.
Arithmetic, dressed up as a dragon hunt.
The short version, with engine noise.
Seven minutes of the engine showing off.
68 projects I've built on my own time, with what each one does, how it is made and where it lives. The deep dives open with the hard problem each project solved.
Open the portfolioThey were not planned as a set, but they ended up leaning on each other.