Who I am as an engineer

I build systems that do real work without me in the room, and then I build the parts that make that safe.

Over the last few months I set up an AI agent on its own server that runs my product and my life admin. It routes what I send it, hands long work to sub-agents, ships to production when I say yes, and asks me about one thing at a time.

Most of my code is now written by agents. My job moved to the part they can't own: the world they work in. That means deciding who owns what, what they may do alone, how they ask me, how a finished job gets noticed, and what counts as proof. I write that down in plain files I can change from my phone, I turn each rule into a tool or a test where I can, and I keep a dated note, in my own words, every time a rule turned out to be wrong.

I came to software sideways. I built an event marketing team from scratch, then founded and ran my own marketing-technology company before teaching myself to code in 2018. I started at a major airline as a contractor in 2020 and became a principal in 2023.

By day I'm a Principal Architect and Developer in that airline's maintenance-technology organization. I sit between architecture and delivery with no direct reports, and I lead through evidence, tools that make other people faster, and decisions framed clearly enough for leadership to act on. The same ideas run there: I built my team an AI toolkit that is read-only by construction, and peers across teams adopted it. I ran fleet-wide app assessments through parallel sub-agents with one orchestrator holding the risky calls. And every claim carries its evidence or a [check].

• 2013 to 2019: I worked as a business operator, built a marketing team from scratch, and then founded and ran my own marketing-technology company.
• 2018: I taught myself to code, with mentors.
• 2019: I took my first developer job working in Python, Django and React.
• 2020: I joined a major airline as a contractor working on planning software.
• 2021: I became a full-time employee and senior developer.
• 2023: I became a principal architect and developer.
• 2025 to now: I serve as an architecture and cross-team technical lead, running agents at scale at work and at home.

Why it matters: the operator years are why I start from the outcome, not the technology.