Data Engineering · Business Intelligence · Data Architecture
Translating complexityinto meaning,and meaning into systemspeople can trust.
The public thinking space of a systems architect working across data engineering, business intelligence, and customer impact. Essays, frameworks, and field notes on building things people are willing to act on.
The Translation Map — messy → modeled → trusted
The Architecture You Remove Still Has to Exist
Teams often celebrate removing components, abstractions, or processes in the name of simplicity. The harder question is where the responsibility moved. Complexity rarely disappears. It usually changes ownership.
The Rules You Never Wrote Are Still Running Your System
Teams often believe they are debating architecture when they are really discovering undocumented business rules. Making those rules explicit is one of the highest leverage activities in building systems that people can understand, evolve, and trust.
The Customer Is Always Somewhere in the Data Model
It's easy to treat a data model as a purely technical artifact. But every table, every default, every simplification quietly distributes benefit and friction among real people. Naming that distribution is part of the job.
Architecture Is What Still Works After the Diagram Meets Reality
A clean diagram is a hypothesis about a system that doesn't exist yet under conditions that haven't arrived. Real architecture is defined by how the design behaves under the stress vectors you know are coming.
All thinking →Trustworthy Data Systems
A data platform earns trust the way a person does: by being accurate, by being able to explain itself, and by keeping what it's told safe. Writing here is about building systems people are willing to act on.
2 pieces§02BI as Decision Infrastructure
Business intelligence is not decoration. It is the load-bearing structure under the decisions an organization makes every day. These notes treat dashboards and metrics as infrastructure, with the reliability standards that implies.
1 piece§03Architecture Under Pressure
A diagram is a hypothesis. Architecture is what is left standing after that hypothesis meets real load, real deadlines, and real people. This theme is about designing for the moment the pressure arrives.
3 pieces§04Practical AI for Builders
Most useful AI is unglamorous: it assists, explains, and removes friction long before it automates anything. Writing here is about adopting AI in a way that compounds trust instead of spending it.
1 piece§05Customer Impact
Somewhere at the end of every pipeline is a person whose experience got better or worse. This theme keeps the human consequence of technical decisions in view — because the customer is always somewhere in the data model.
1 piece§06Systems and Meaning
The throughline of everything here: translating complexity into meaning, and meaning into systems people can trust. Reflections on the craft of making complicated things legible.
0 piecesSix frameworks I keep reaching for
Reusable thinking, each rendered as a schematic rather than a bullet list.
Custom Website Building
Fast, modern, professional websites that get a mission online — and stay easy to live with.
Read more →The Nonprofit Back-Office
One platform to run a small charity — website, shared inbox, photos, and donations — without a team of staff or a stack of subscriptions.
Read more →One gets you online. The other keeps you running.
Building something that has to be trusted?
I'm always glad to compare notes with people who care about systems other people can rely on.
Get in touch