About
Thirty years, never the same job, always the same work: join a team, roll up my sleeves, and listen. How do people actually do things - not how the org chart says they should? Where are the opportunities to improve? I don't show up with solutions. I show up with empathy and questions. Everyone at every level has a piece of the story, from leadership to the person filling out the forms. The picture only becomes clear when you've heard all of them.
I left my last engineering job in January 2026 and, instead of sending resumes, opened a new /src folder to find out what one engineer could build with AI agents.
Nine weeks later there were products in production. Six months later there is a suite of them: an AI code-review tool, energy-rate tooling for community solar, an open-source publishing framework, a self-hosted media transcoder, and a deterministic pipeline that drives AI coding agents through plan, build, test, review, and commit. There is a peer-to-peer lending app with native iOS and Android clients in the final stretch before launch. The whole personal stack runs for about two dollars a month.
What I learned is how to build with agents for real: specs, architecture, cost-aware model selection, and review discipline. Not vibe-coding, but software I will put my name on. What I already knew, from 30 years across manufacturing, aerospace, logistics, and clinical diagnostics, is how to drop into an unfamiliar domain, listen to the people with the problem, and turn what they need into something that ships.
I built the independent practice to go deep on this. Now I want to do it inside a team, ideally one adopting or scaling AI, where specs, delivery, and turning ambiguity into working systems are the job.
I start by watching. How does your team actually work? Not the documented process - the real one. The workarounds, the copy-paste steps, the "we've always done it this way" habits. That's where the opportunity is.
I measure it, test a fix, and iterate until it works. Sometimes the fix is AI. Sometimes it's a script. Sometimes it's rearranging when something happens. The tool doesn't matter. The result does.
How I work with agents
I architect and spec. I direct AI agents through implementation. I read, review, and debug everything that ships. The products are the proof, and the code is public where it can be.
Off the clock
I built a mountain home
Managed and personally built a house in Welches, Oregon. Oversaw everything from excavation to certificate of occupancy. Turns out a build is a build.
I'm a data nerd
Telemetry and sensors driving decisions just makes sense to me. My house is a Home Assistant lab, and it is where the solar integrations get stress-tested before anyone else runs them.
I jumped out of a perfectly cromulent airplane
Once. It embiggened me.
Let's work together.
Whether it's shipping a product, fixing a broken process, or figuring out where AI actually helps - I'd like to hear about it. I'm open to full-time engineering roles.