Data, operations, and strategy.
Turning complexity into clarity.

I design and build systems — technical infrastructure, AI pipelines, data architectures, and the documentation that holds them together.

My work sits at the intersection of engineering and editorial thinking: building things that work, then explaining how and why they work in ways that create leverage for teams and organizations.

I believe the best technical work happens when you treat architecture as a design discipline — where clarity of thought produces clarity of system.

Architecture is the art of making infrastructure legible.

Systems First

Every problem is a system problem. The code is an artifact of the thinking behind it.

Clarity as Feature

If a system can’t be explained, it can’t be trusted. Documentation is architecture.

Intentional Complexity

Add complexity only when it solves a real constraint. Everything else is noise.

Build to Learn

Shipping is a form of research. Each project is a hypothesis about how systems should work.