Full-Stack Clarity
Why the Most Important Line of Code Is the One That Explains What It Does
Coming soon.
“Data models are perhaps the most important part of developing software, because they have such a profound effect: not only on how the software is written, but also on how we think about the problem that we are solving.”
— Martin Kleppmann, Designing Data-Intensive Applications, Ch. 2 (O’Reilly, 2017)
The premise
Data teams build pipelines. Content designers write the words. But the fastest-growing gap in tech isn’t between code and copy. It’s between what data means and what people think it means.
This book argues that content design and data engineering are the same discipline at different layers of abstraction. The glossary is a semantic model. The error message is a decision framework. The column name is a vocabulary decision. And the documentation layer isn’t downstream of infrastructure — it is infrastructure.
Drawing from years of designing the language layer of Microsoft’s data platform, mentoring builders at hackathons, and teaching at the intersection of content and data, Full-Stack Clarity gives practitioners a framework for designing meaning into data systems — not as an afterthought, but as a core engineering practice.
Who this book is for
- Content designers who want to go deeper than the UI layer
- Data engineers who know their documentation is a problem but don’t know how to fix it
- Analytics engineers building semantic layers and metrics definitions
- Product managers on data-heavy teams who need a shared language with both content and engineering
- Anyone who’s ever asked “what does this column actually mean?” and not gotten a clear answer
What’s inside (working chapter outline)
- The Documentation Layer Is Infrastructure — Why data projects fail at meaning, not at code
- Schema Is Language Design — Every naming decision is a content decision
- SQL as a Content Skill — Reading and writing queries as comprehension exercises
- The Glossary-to-Model Pipeline — How terminology becomes computable definitions
- Metrics, Measures, and Meaning — Why “what is an active user?” is a content design problem
- Writing for Machines — Metadata, AI agents, and content design for non-human audiences
- The Data Product Audit — A framework for evaluating any data product’s content layer
- Full-Stack Clarity — Tracing a concept from raw data to user understanding, end to end
Get notified
This book is in early development. If you want to know when it’s available — or when early chapters are shared — leave your email and I’ll keep you posted.
“The most important line of code in any data pipeline is the one that explains what it does.”