About me

Primarily remote, happy to go into the office a day or two a week. I often have headphones on. Always feel free to interrupt: I’m never not happy to chat.

I can be my own worst critic, and when things aren’t sitting right I’ll sometimes go quiet rather than say so. Don’t take it personally. If something’s off, it’s better to ask.

I’m a dad, which means there are occasional hard stops in the afternoon. I’m always available async, and I’ll always make my time up.

• Fewer meetings, clearer decisions
• Being prepared: for projects, for meetings, for conversations
• Pairing over mobbing; space to think over constant interruption
• Writing things down
• A clear answer to “why are we doing this”

I work well across disciplines. I can talk to designers about what’s buildable without rubbishing the idea, and to engineers about design without losing sight of what needs building.

I’m direct. I’ll tell you when I think something’s wrong, and I’ll try to explain why rather than just asserting it. I’d rather argue about it early than nod along and watch it fall apart later.

I take documentation seriously. It’s how decisions outlive the people who made them, and it cuts the bus factor.

Workshops are my thing. If you’re running one, get me involved. If I’m running one, get stuck in.

Face to face is best, or a call if not. Any format works, so long as it’s timely and specific. Vague feedback is hard to act on.

I’m not a full-stack generalist. I have opinions about back-ends and I’ll share them, but I don’t build them.

I’m not interested in complexity for its own sake. If the simple thing works, we should do the simple thing.

I’m no good in places where the calendar is always full and the direction keeps changing. Too many video calls, too much context switching, too little room to actually think: that’s where I start to struggle.

I do my best work in the mornings and again in the late afternoon. Midday is where my focus drifts. Async suits me well: I’ll read and reply at odd hours, but I won’t expect a reply outside your hours.

Proper front-end: HTML, CSS, the platform. Accessibility and inclusive design. Getting what design meant and what engineering built to match. The unsexy infrastructure work everything else sits on: naming conventions, token architecture, contribution models. I do some of my best work on the things nobody else wants to look at.