About Me

Hi, I’m Shawn.

I write about software architecture, engineering judgment, and the decisions that shape real systems. My technical background is in distributed systems, event-driven architecture, and real-time software—especially systems that need to keep working as scale, complexity, and organizational pressure set in.

Over time, I’ve become just as interested in the forces around software as the code itself: why systems get harder to change, how teams trade long-term coherence for short-term motion, and what separates software that merely functions from software that actually holds up.

That perspective comes from working across architecture, backend systems, infrastructure, frontend development, and product delivery in real environments.

I’m based in Minnesota (hence the TLD), and this site is where I share essays, technical writing, and ideas on what matters most in modern software.

What You’ll Find Here

You’ll find writing on software architecture, event-driven systems, quality, delivery, and the broader patterns that shape engineering work over time. Some posts stay close to distributed systems and Kafka; others explore software strategy, judgment, and the changing shape of software development.

Some of it is technical. Some of it is strategic. Some of it is opinionated on purpose.

The throughline is simple: I care about software that stays coherent under pressure, resilient as it grows, and worthy of trust.

Why I Write

There’s no shortage of content about tools, frameworks, and implementation details. I’m more interested in the layer above that: how systems stay understandable, how good decisions get made, and how teams keep software aligned with reality as complexity grows.

That’s the territory I tend to explore here.

Thanks for reading.