Quality code is downstreamof quality system design.
I design the architecture and then I build it, which means I have to live with my own decisions. Fourteen years of production systems — payments, telemetry, multi-tenant platforms — most of them still running without me.
14
Years in production systems
31
Systems shipped and handed over
99.97%
Uptime across current engagements
0
Of my rewrites have been rewritten
01 — 2025
Ledgerworks
An event-sourced double-entry ledger, replacing a spreadsheet that had opinions.
Read the case →
02 — 2024
Tideline
Telemetry ingest for 12,000 vessels, built to survive the satellites it depends on.
Read the case →
03 — 2024
Northgate
Tenancy and authorization for a B2B platform that had been guessing until then.
Read the case →
04 — 2023
Cadence
Constraint-based dispatch for 900 field technicians, re-solved on every event.
Read the case →
05 — 2023
Slate
The paved road for forty engineers: one way to create, ship and observe a service.
Read the case →
06 — 2022
Meridian
A nine-year-old monolith taken apart while it kept trading. No feature freeze.
Read the case →
I draw boxes and then I have to build them
Most architecture goes wrong at the handoff: someone diagrams a system they will never have to operate, and someone else discovers the diagram was a wish. I do both halves — the design gets tested by the implementation, and the implementation gets tested by two years of on-call.
Architecture
Backend
Data
Operations
Got a system that needsdesigning properly this time?
Contracts from six weeks. I read every enquiry myself and reply within two working days, usually with an awkward question about your data model.