The hard part of building software is no longer writing the code.

I lead frontend teams at CrowdStrike, building security tooling used by thousands of organisations. My work spans architecture, developer tooling and quality systems. I build products independently to stay close to the craft and test ideas against real problems.

Code is getting cheaper to produce. The things around it are not.

How I work

How do you keep quality high when the system is changing faster than any team can manually review?

  1. Teams built around ownership, not process

    I lead frontend engineers and SDETs. The focus is on giving teams enough context and autonomy to make good decisions without waiting for permission. Structure matters, but only if it creates clarity rather than overhead.

  2. Architecture that absorbs change

    Frontend systems at scale need to handle constant change without accumulating debt. I focus on performance budgets, observable behaviour and build systems that are part of the product, not afterthoughts.

  3. Tooling as infrastructure

    Developer experience is not a perk. When local development, CI pipelines and testing feedback are fast and reliable, teams move faster and make fewer mistakes. I treat this as core infrastructure.

  4. Quality built into the system, not bolted on through review

    I work with SDETs to embed quality into architecture and automation. Accessibility, visual regression and test coverage should be structural guarantees, not things that depend on someone catching them in review.

  5. AI in the development lifecycle

    I'm bringing AI into how we build software. Not as a novelty, but as a reason to rethink what pipelines, specifications and review need to look like when code is cheap to produce and expensive to validate.

Products

Writing