I've been shipping production software for fourteen years—since well before any of this got called "AI." Now I build agents that keep the craft, the judgment and the accountability firmly human.
Right now everyone in my field is asking the same question: will the machines replace the engineers?
I think that's the wrong question.
Here's what's actually true. The agent can write the code now. What it can't do is decide what's worth building, hold the line when the easy answer is the wrong one, or stand behind the thing when it breaks at 2am. That part is still mine. I think it always will be.
So the work I care about isn't automating engineers out of existence. It's the opposite: figuring out what a human should keep as the machines get good, and getting very good at that part. Judgment. Taste. Architecture. Accountability. The craft doesn't disappear. It moves up a level.
One belief sits under all of it: your tools should belong to you. The AI I lean on most runs entirely on my own machine. My notes, my work, my second brain: none of it phones home.
So this isn't a resume. It's what I believe, and the things I've built because I believe them.
Candice is my family's private AI, and she's not a toy — a production multi-agent system on an orchestration layer I built: real tool use, long-term memory, multi-step reasoning, and a check-with-me-first step before she does anything that matters. This page was built with her.
Most of them I use every single day. They are scrappy right now, yes. But none of them are demos.
I've always been the lead who still writes code, never the manager watching from a distance.
Line-managed senior engineers while staying hands-on in Laravel, ReactJS and in-house MVC frameworks.
Built Laravel, ReactJS and MinIO-backed applications from the ground up.
Project lead on a J2EE financial web app for a Japanese client.