Colophon
About this studio
This is a working notebook on data architecture — the discipline of deciding how information is shaped, stored, moved, and trusted inside an organisation.
I’m a working data architect. I spend my days drawing the boundaries between systems: where a fact lives, who owns it, what it’s allowed to mean, and how it survives contact with a hundred downstream consumers who each want it slightly differently. This site is where I think out loud about that work.
What you’ll find here
Essays and field notes, roughly in three registers:
- Manifestos — opinionated arguments about how data work should be done.
- Field notes — practical, evergreen explainers on modeling, pipelines, and design patterns.
- Reconsiderations — second looks at popular architectures, including where they quietly fail.
I write for practitioners. The goal is not to be comprehensive but to be useful — to leave you with a sharper mental model than you arrived with.
The premise
Most data problems are not technology problems. They are problems of structure and agreement: someone defined “active user” three different ways, no one owns the orders table, and the warehouse has quietly become a museum of every decision nobody wanted to make. Good architecture is mostly the courage to make those decisions explicit, and the discipline to keep them that way.
That’s the thread running through everything here.
Built with Jekyll, hosted on GitHub Pages, and set in Fraunces, Newsreader, and IBM Plex Mono. The source lives on GitHub.