Notes on dataarchitecture.
Short essays on architecture, cost, hiring and AI: one cartoon, one idea, most days of the week. No tutorials, no listicles.
When You Actually Need a Semantic Layer
Most teams buy a semantic layer the way they buy a data warehouse. Tool first, problem retrofitted.
Read →Data mesh is an org design pattern. Here are the 5 things you need before you st
Data mesh is an org design pattern. Here are the 5 things you need before you start.
Read →Everyone says "people, process, technology." Then they start by picking Snowflak
Everyone says "people, process, technology." Then they start by picking Snowflake.
Read →You have 47 data quality issues. You can fix 5 this quarter. Here's how to pick
You have 47 data quality issues. You can fix 5 this quarter. Here's how to pick the right 5.
Read →Your data platform has 6 vital signs. Most teams only check 2 of them.
Your data platform has 6 vital signs. Most teams only check 2 of them.
Read →Hybrid work changed how your data team collaborates. Nobody adjusted the archite
Hybrid work changed how your data team collaborates. Nobody adjusted the architecture decisions for it.
Read →Consolidating from 15 tools to 7 in 2026. Three drivers, none of them innovation
Consolidating from 15 tools to 7 in 2026. Three drivers, none of them innovation.
Read →Most data catalogs go stale within a quarter. The teams that prevent it do one t
Most data catalogs go stale within a quarter. The teams that prevent it do one thing before procurement.
Read →Choosing between 3 data platforms? Stop comparing demos. Here's the radar chart
Choosing between 3 data platforms? Stop comparing demos. Here's the radar chart that makes it objective.
Read →Your data platform has 15 incidents per month. Is that normal or a crisis? Here'
Your data platform has 15 incidents per month. Is that normal or a crisis? Here's the benchmark.
Read →Want expert eyes on your data architecture?
No pitch. An honest conversation about whether I can help, and what shape it would take if I can.