About

The through-line has been the same problem: how do you build frontend systems that stay fast, reliable and maintainable as everything around them changes? The tools shift. The frameworks come and go. The underlying challenge does not.

What has changed is the economics. AI has made producing code cheap. Architecture, testing strategy, specifications and team judgement have not. They matter more now than they did before. Most teams are still optimising for a cost structure that no longer applies.

I build products on the side to stay close to the craft. It is easy to lose that connection when you spend most of your time leading teams. Building things keeps me honest about what is actually hard.

Background

Before CrowdStrike, I worked across several industries. Each shaped how I think about building software.

At Telegraph Media Group, I worked on the frontend platform serving millions of readers. Performance at that scale is not optional. It taught me that architecture decisions made early compound for years.

At Houseful, I led frontend architecture and the replatforming of Alto, an estate agency product used across the UK. That meant consolidating shared UI systems, improving build performance and establishing accessibility standards that held across the organisation.

At TUI, I built booking and search experiences for specialist travel brands under real commercial pressure. Systems that are slow or unreliable lose money visibly and immediately.

At Jagex, I led a team building the web platform and internal tooling for RuneScape. That was where I first learned how platform work differs from product work.

How I think about engineering

I care about how frontend systems behave at scale. That means codebases that remain understandable, performance and behaviour that are observable and teams that can work independently without creating fragmentation.

Strong typing, build tooling and testing strategy are not additions to the system. They are the system. When these are treated as optional, quality becomes a matter of individual discipline. When they are structural, quality becomes a default.

I think the most important shift happening in software development right now is the move from code as the primary output to specifications, constraints and validation as the primary output. AI is making code cheap. The teams that invest in everything around the code will be the ones that benefit most.

I write here about systems, tradeoffs and how software gets built at scale. You can find me on GitHub or LinkedIn.