Skip to content

The person behind the work

How I learned the craft, what I work with, and what I hold to.

01Story

Self-taught, then tested.

I taught myself to program, with a terminal and a lot of patience. With trial, error, and the slow satisfaction of understanding how a system really works.

That habit carried me through startups, where everything is urgent, and into enterprise teams, where everything is large. Each taught me something the other couldn't.

Now I work where design and engineering meet. I don't only follow blueprints; I draw them, from a working sense of how software holds up in real use.

Code is instructions for a machine, and a language for ideas.

02Tools

What I work with.

The tools I reach for most, grouped by where they sit.

  • Frontend

    • Flutter / Dart
    • iOS / Swift
    • Android / Kotlin
    • Next.js

  • Backend

    • Node.js / Express
    • PostgreSQL

  • DevOps

    • GCP
    • Docker
    • CI/CD
    • Vercel / Cloudflare
    • Firebase / Supabase

  • Design

    • Figma
    • Design systems
    • Claude Design
    • Prototyping
    • User research

03Principles

Three things I hold to.

  1. 01

    Precision is the standard.

    I put architectural soundness ahead of the rush to ship. Every decision is deliberate, so the system holds up long after launch.

  2. 02

    Design is engineering.

    A good interface is a system. Type, spacing and colour follow rules as strict as any code, and deserve the same care.

  3. 03

    Build for change.

    Requirements move. I build systems that can bend, scale and adapt without being rebuilt.