I am a staff engineer at Fueled, working on large-scale WordPress and platform projects. I sit somewhere between architecture, developer experience, and the day-to-day realities of shipping software with real teams and deadlines.
Most of my work lives in that middle layer where requirements are fuzzy, systems are old, and people still need to ship calmly. I like taking messy constraints and turning them into clear structures that engineers can rely on.
What I do
Right now, I work as a staff engineer on complex WordPress and platform builds. That usually means:
- Designing and evolving architectures for large editorial and content-heavy sites.
- Helping teams modernise legacy WordPress codebases without breaking what already works.
- Building tools, CLIs, and internal frameworks that make it easier for engineers to do the right thing by default.
- Pairing with engineers on tricky problems and helping turn “this feels fragile” into “this feels boring and predictable”.
Before returning to a staff engineer role, I spent time as an engineering manager. That experience strongly shaped how I think about communication, tradeoffs, and the difference between “the right design” and “the design we can actually ship with this team right now”.
How I think about engineering
I have spent most of my career working on WordPress at scale. Multisites. Legacy codebases that need to evolve. Editorial teams with sharp workflows. My focus is on the foundations that let those systems change safely.
I am interested in how AI fits into that work in a real, practical way. Not as a toy, but as a teammate that handles the repetitive glue while humans shape the architecture and constraints.
Some principles I try to work by
- Clarity beats cleverness. If I cannot explain it, we should not ship it.
- Structure reduces ambiguity. Typed inputs and outputs make AI and humans both more reliable.
- Developer experience multiplies output. Friction is a tax on every project.
- Calm systems win. Good architecture makes change boring instead of risky.
- AI works best with guardrails. Use it where patterns are clear, and feedback loops are tight.
Things I have built or maintained
A few of the tools and libraries I have worked on over the years. Some started as client needs. Most exist to make engineers lives a little easier.
- Safe SVG – A WordPress plugin that lets you safely upload SVG files to the media library by sanitising inline SVG content. View on wordpress.org →
- SVG sanitiser library – A PHP library that strips unsafe elements and attributes from SVGs so that teams can rely on vector assets without worrying about security surprises.
- wp-scaffold – A starting point for modern WordPress projects, with structure, tooling, and patterns that aim to reduce friction for teams working across multiple codebases.
- DX and CLI tooling experiments – Internal tools for commands, scaffolding, and AI assisted code generation that try to bake good defaults into the everyday developer workflow.
Speaking and writing
I like sharing what I learn, especially around migrations, AI-assisted workflows, and developer experience. I have spoken at events like WordCamp London, and I write on this site whenever I have something valuable enough to be worth someone else’s time.
If you are interested in having me talk about AI in engineering, DX, or modern WordPress architecture, the easiest way to reach me is through the links at the bottom of this page.
Outside of work
I live in Cornwall with my family. When I am not thinking about code, I am usually being climbed on by my daughters, planning future projects, or recovering from Brazilian Jiu-Jitsu training.
Long term, I like exploring ideas that sit at the edge of software, games, and real-world experiences, anything that helps people understand systems a little better, or gives them a calm place to think.