About
Engineering leadership, technical strategy, and systems that have to survive real conditions
I'm an engineering leader and writer focused on the intersection of technology, people, and the systems that connect them.
Most of my work has been about helping teams navigate complexity that does not stay politely technical. It shows up as scaling pressure, unclear ownership, communication debt, architecture drift, and decisions that make sense locally but compound badly over time.
I care about how systems behave under stress: codebases, teams, organizations, and the narratives people use to understand what is happening. That is the throughline behind the writing, the mentoring, and the kinds of conversations I tend to be most useful in.
What I Help With
Leadership Under Pressure
Helping engineering teams and leaders make better decisions when scope grows, ownership blurs, and systems become harder to reason about.
Architecture With Consequences
Connecting technical architecture to organizational realities, so strategy is grounded in how teams actually build and operate software.
Narrative as a Thinking Tool
Using writing and structured explanation to make complicated systems easier to understand, communicate, and improve.
Why This Perspective
- Two decades working across software delivery, architecture, and engineering leadership
- Writing across leadership, technical systems, AI tradeoffs, worldbuilding, and tabletop design
- Advisory work that favors practical judgment over abstract playbooks
I also write in the World of Artumin, where strategic and leadership ideas get tested through narrative rather than direct argument.
Who This Is For
If that sounds close to the problems you are working through, the best next step is a direct note about your situation and what kind of conversation would be useful.