Systems are only one part of how I see the world.
Outside operational systems and architectural thinking, I am deeply interested in philosophy, fiction, movement, narrative structures, exploration, and the way people coordinate around ideas.
The same curiosity that drives my interest in information flow and organizational systems also appears in fantasy worlds, process philosophy, travel, dance, and the strange ways humans create meaning collectively.
I am less interested in mastering a single discipline, and more interested in understanding how seemingly unrelated systems — technical, human, philosophical, or fictional — begin to mirror each other under enough complexity.
The systems mindset did not emerge from engineering alone.
Many of the ideas that shape how I think about architecture, coordination, and operational systems were formed outside software entirely. Hover any card to find the question hiding inside it.
I've become increasingly interested in the places where technical systems, human coordination, narrative structure, and philosophy begin to overlap.
Most of my work eventually traces back to that curiosity.
The same questions, appearing repeatedly.
My interests were never random. Biology, complexity, information, architecture, and organizations were simply chapters of the same investigation.
For a while, I thought I was interested in biology.
Biology was the first place I encountered systems that could coordinate without a central controller. I spent hours reading about cells, self-organization, and how feedback loops allow life to adapt and maintain balance without a single authority.
Later, I thought I was interested in complex systems.
The more I studied complex systems, the less convinced I became that outcomes could be understood by examining individual parts alone. Order arises spontaneously from simple rules playing out at scale, and complexity is something that must be allowed, not micromanaged.
Then information systems.
Eventually my attention shifted from the components themselves to the signals moving between them. I realized that a database node, an API gateway, or a cell signaling path are all governed by the same constraints of flow, noise, and consensus.
Then architecture and infrastructure.
Structure stopped looking like an implementation detail and started looking like the thing that determines behavior. Physical layouts, transit lines, and database schemas are desire lines—the physical pathways that guide how energy and data flow.
Then human organizations.
Whether coordination is technical or social, it fails at the same boundaries where context is lost. Teams scale, align, or fail under the same mathematical constraints as software clusters. Human organization is just another distributed network.
Eventually I realized the subject kept changing, but the questions did not.
The interests were never random. They were chapters of the same search: how do independent entities cooperate, how does flow shape behavior, and how do systems scale without collapsing? I was looking for the hidden structure beneath coordination itself.
Over time, the focus shifted away from individual disciplines and toward the patterns beneath them.
Software, organizations, cities, biology, philosophy, and infrastructure all appear profoundly different on the surface. Yet they repeatedly raise variations of the same underlying questions.
Questions about information flow. About coordination under uncertainty. About the emergence of complexity, the constraints of structure, and the breaking points of scale.
I haven't found definitive answers to these questions, and I am increasingly doubtful that such answers exist.
But the territory is becoming more familiar. The search has become clearer. And everything I build, write, or study now is just another attempt to trace those patterns a little further.