Experience
Nearly 20 years
Software, systems, and leadership
My work sits between technical direction, product judgment, and delivery. That usually means architecture, prioritisation, team direction, and clear tradeoffs under real constraints.
I value strong technical foundations, but I do not romanticise them. Good engineering has to survive business pressure, limited time, and imperfect information.
I also publish open-source work. It is a public record of how I think, build, and maintain software.
What I do
Engineering leadership
I set technical direction, keep delivery honest, and make tradeoffs clear enough for teams and the business to act on.
Founder and operator work
I work close to product and business constraints. The technical choices need to support real outcomes, not just clean diagrams.
Hands-on systems work
I still care about the implementation. I am drawn to systems that need to be robust, legible, and worth maintaining.
Principles
How I think
Strategy without execution is theatre.
Architecture matters, but timing matters too.
Small teams need clarity more than process.
Technical decisions should be legible to the business.
Open source is most valuable when it reflects work people would actually maintain.
Focus
Areas I focus on
Engineering leadership
Product and technical strategy
Architecture and systems design
SaaS and product execution
Open source
Applied AI, evaluation, and reliability
Rails and pragmatic backend systems
Building something that needs judgment and execution?
I am interested in hard problems that need product judgment, technical depth, and steady execution.