Engineer who runs the project. Project lead who still writes the code.

I grew up around makers — the kind of people who insisted that a job is not done until it’s tidy. That bias has carried into everything I do. I studied computer science, then bent slowly toward the parts of software engineering and project management that don’t fit in a single discipline: writing software, managing the people building alongside it, and shaping the brand that sells it.

Right now I lead the build of a renewable-energy simulation platform for Vanko Group under RPL Central — live at powerpioneers.net. The engine runs on real-time data and fires live scenario events as the weather shifts. I led a team of five through scope, architecture, and the build itself.

Around that, I keep a small practice in software that solves narrow, useful problems — agentic workflows, a marathon training planner driven by voice notes, a personal health platform, an RFQ-to-quote parser, and a console-based payroll system. Selected work lives on the projects page.

• —
  Specific over clever.

  Boring tools beat clever ones at scale.
• —
  Schedule is a feature.

  Finished things ship; perfect things don’t.
• —
  Field-first.

  The closer to the actual work, the better the decisions.
• —
  Quiet design.

  Restraint reads as confidence. Avoid the AI-glow.

I photograph the cities I find myself in. I read more architecture writing than I probably should. I cook with a single sharp knife. I enjoy the leisure of video games if I have time. I keep a running list of small problems that deserve good software — most never get built, a few do.