Technology Leadership · Data Platforms · Engineering Organisations
I build data platforms, but the platform is rarely the whole problem.
Over the last decade I've worked across healthcare, education, fintech and energy, usually somewhere between the architecture, the team and the business pressure around it.
The bit I keep coming back to is how organisations decide what they need from technology. Why some teams earn trust quickly. Why good engineering can become invisible. Why a sensible platform can still turn into a bottleneck if nobody shares the same picture of what it is for.
This site is where I write those lessons down while I'm still close enough to remember the awkward bits.
These are the ideas behind how I build data platforms and engineering teams: where trust is won or lost, how technical choices age, and what it takes for technology to stay useful once real organisational pressure arrives.
I didn't get into technology because I loved databases. I got into it because I liked taking complicated things apart until they made sense. It turns out the most interesting systems I've worked on were usually the organisations around the databases.
More →What I'm working on, reading, avoiding, learning and trying to get clearer about. Updated when it feels like the old version has stopped being true.
See what's current →