About Christian

I'm Christian. I build things that help people do things together: work, create, learn, and experience something they could not make happen alone.

Sometimes the thing I build is a developer platform or an AI system. Sometimes it is a way for a team to make decisions, a clearer boundary around responsibility, or the context that lets someone contribute with confidence. Sometimes it is hands-on work in a volunteer camp, alongside the people who will use what we are building. The medium changes. I keep coming back to the conditions that make working together possible.

My technical work has taken me through ML infrastructure, autonomous-vehicle simulation, collaborative hardware, and developer platforms in healthcare. Across those settings, I have repeatedly found that the software and the human organization shape each other. A technical problem can expose unclear ownership. A process can hide a missing capability. A person repeatedly rescuing the work can be the signal that the surrounding system needs to change.

I like being close enough to the work to notice those connections and able to act on them. That means moving between implementation, product judgment, operations, organizational design, and conversations with the people involved. It also means knowing when another person's expertise is what the problem needs.

Why this matters to me

The reason underneath is personal. I want the people around me to be able to show up fully, without losing so much energy to fragmentation or having to become the permanent workaround for a broken system.

The bakery I grew up in was an early experience of work, community, and life belonging together. That thread is still present in how I think about platforms, teams, and the volunteer community at Titanic's End. Building the infrastructure and keeping the joy alive are connected responsibilities. So are having a useful plan, supporting someone through a hard moment, and making room for others to take initiative.

Care is part of the work. So are craft, clear decisions, honest feedback, and the willingness to change something when it stops helping.

What I am developing here

I use System of Work as the working name for an evolving model of these connections: how intent, context, trust, responsibility, tools, and learning shape what people can do together. Human–AI collaboration gives those questions new urgency and new possibilities. The model also has to remain useful in a conversation, a team, or a physical build where AI may have no role at all.

This space is where I make the work inspectable. I publish things I have built, decisions and experiences I have learned from, practical approaches, and investigations that are still taking shape. A case can show where an idea came from. A guide can make it usable. A working paper can expose the questions I have not answered yet.

I want the work to be useful at different depths. You should be able to take one idea into your own setting, follow it into the evidence, or challenge the model with something it does not explain. Teaching, coaching, and exchanging experience matter to me because another person's questions often reveal what my own context has made invisible.

I am drawn to people and organizations that take both the quality of what they build and the lives of the people building it seriously. This is an invitation to see how I work and to find the part of it that connects to what you are trying to do.