I build things, and I care whether they actually work.

I started out in game programming, mostly C++ and Unity. Games are honest with you about whether you got it right: the thing either runs smoothly or it very obviously doesn’t, and there isn’t much you can say to talk your way around a broken frame rate. I think that’s where the habit of caring whether something actually works came from, and I’ve carried it into everything I’ve built since.

I use AI-assisted tools to move quickly, though most of my time on these projects went into the things the quick version left out. On Asteroids that was a leaderboard the browser could have typed a fake number into. On Tally it was a dashboard that hid other users’ invoices on screen while the database would still have handed them over. On Parsel it was an AI feature that would have come apart the first time someone pasted in something that wasn’t a job posting. None of them were hard to fix once I went looking, and I would much rather find that sort of thing myself than have someone else run into it later.

So the way I work isn’t complicated. I get to something that runs as quickly as I can, and then I slow down and spend real time on the parts I wouldn’t be comfortable leaving as the fast version left them. Each project page below says which parts those were, and where I know the work is still unfinished.