Software engineer in London, fifteen years in, building software ventures since before I was twenty. What you will find here are decisions from systems that are already running: what I believed, what broke, what I changed, and the numbers after. Nothing in progress, because I can only talk about a thing once it is built and I am happy with it. This is how it works for me.
Writing
Oct 2026
I set out to build an AI-native product and had to build Lumo first: a real problem, an MVP that broke on money, a rebuild around a ledger, and three studios of data before AI could mean anything.
Sept 2026Case study
The accounting core of Lumo, taken out as tenant-ledger, a package on npm, to test whether its boundary was real. It was. Reviewing it on its own found an allocation race production had never shown, proved it on two connections, and sent the fix back.
Sept 2026Case study
Multi-tenant scheduling, enrolment, attendance and billing for dance studios, built and operated solo. The architecture, the decisions I had to argue myself out of, and what the first months in production changed, with the numbers.
Now
By day I lead full-stack delivery for The Open University at Innova-tsn.
Evenings and weekends go to Lumo, software for dance studios that I built alone and run alone, and because I am the one who gets called when it misbehaves, every shortcut I take I also have to operate. The thinking ends up here.
Separately, I have been finding out how far an AI-assisted workflow goes, and where it fails.