Your Data Model is Your Destiny
I recently read a post by Matt Brown titled "Your Data Model is Your Destiny" that resonated with me deeply. In his post, Matt discusses the importance of the underlying data model of any system or product we interact with, and how it shapes our experience and the value we derive from it. He uses several examples to illustrate his point, including Slack, Notion, and Figma.
His observations align with my experience as a technology architect, but I could never quite articulate the fundamental importance of data modeling/design until I read Matt's post and his brilliant examples.
It rare when speaking about system or application architecture that the underlying data model is front and center. Yet, as Matt points out, the data model ultimately determines how effectively one can deliver functionality and create value. Use the wrong data abstraction, and clever engineering won't make up for it.
Matt also makes a key point that the world of AI agentic coding code is cheap/abundant. However, if the data model is poorly designed, no amount of code generation or AI assistance will correct or overcome that issue. Coversely, a unique insight about a process or domain when properly modeled, can unlock significant product value - it can be the "moat" that competitors will have to cross.
I won't steal all his thunder: Highly recommended read for anyone involved in product design, architecture, or development.