Systems & Architecture
Building technical systems that make sense as a whole, not just one component at a time.
Technology · Systems · People
Better systems begin with seeing the whole picture.
I write about technology, architecture, and the people who live with the systems we build.
After more than two decades in software engineering, I've learned that the hardest problems rarely exist in isolation. They emerge from the relationships between technology, workflows, organizational decisions, and the people on the other side of the screen.
My work is about understanding those relationships, asking better questions, and finding ways to change the system at its source.
The point of view
The problems behind the problems.
We spend a lot of time fixing things. Sometimes we need to step back and ask why they keep breaking.
I'm interested in what happens when we look beyond the immediate task and examine the larger system: how people work, how decisions get made, how content moves, and how technology either supports or frustrates all of it.
What I think about
Four ways into the whole picture.
Content & Platforms
Designing content management platforms around the people who create, manage, publish, and maintain content.
Human-Centered Engineering
Treating accessibility, usability, and maintainability as engineering responsibilities, not finishing touches.
The Human Side of Tech
Exploring leadership, collaboration, organizational friction, and what it takes to do good work with other people.
Notes from the work
Ideas I'm exploring.
A few questions I'm working through. Essays will find their way here as they're ready.
Architecture Is Easy. People Are Hard.
The hardest part of a technical system is often everything surrounding the code.
Stop Fixing Symptoms. Fix the System.
What changes when we stop treating recurring problems as isolated incidents?
Accessibility Is an Engineering Responsibility.
Inclusive experiences depend on decisions made long before the final interface.
These are working ideas, not published essays. More soon.
A little about me
I still care about the code.
I just care about what surrounds it, too.
I'm a software engineer and technical architect who has spent my career building and improving systems, from public-interest digital services to enterprise content platforms.
Over time, my attention has shifted from individual implementations to the larger questions: how systems fit together, how teams work within them, and how the decisions we make affect the people who depend on them.
My work sits at the intersection of platform architecture, content strategy, human-centered design, and the practical realities of getting good work done.
A developing idea
Human-Centered Engineering.
What changes when we treat the people who build, maintain, and depend on technology as fundamental to the engineering process?
I'm developing this idea into a more practical way of thinking about how we design systems, make decisions, and work together.
For now, it's a question worth exploring.
Start a conversation
Good questions make
better conversations.
Have an interesting problem, a different perspective, or an idea worth thinking through?
I'd like to hear from you.
Email me