About

I work at the intersection of data engineering, business intelligence, and architecture, and the throughline of all of it is a single idea: translating complexity into meaning, and meaning into systems people can trust.

That sentence isn't a slogan. It's the actual job. Most of the complexity I deal with isn't in the technology — it's in the gap between what a system technically does and what a person actually needs to understand, decide, or act on. Closing that gap is the work.

How I think about the work#

I tend to start with the human at the end of the pipeline and reason backward. A dashboard is not useful because it has charts; it's useful when someone can look at it, understand what changed, explain why, and decide what to do next. A data platform isn't successful because the pipelines run; it's successful when someone is willing to stake a real decision on its output. Keeping that person in view is what keeps the technical work honest.

I care a lot about the unglamorous properties: accuracy that holds up over time, systems that explain themselves, failures that are loud and local instead of quiet and global. These are the things that earn trust, and trust is slow to build and instant to lose. A lot of my best work is invisible — the migration that didn't cause an outage, the bad idea a team got talked out of — and this site is partly an attempt to make that kind of thinking reusable.

Why this site exists#

This is a working notebook, not a résumé in disguise. I write here to turn things I figured out under pressure into frameworks and field notes I — and hopefully you — can apply again. The themes are the topics I keep returning to: trustworthy data systems, BI as decision infrastructure, architecture under pressure, practical AI for builders, customer impact, and the broader craft of making complicated things legible.

Everything here is written to a standard I hold myself to: it could be shared with a peer, a recruiter, or a former coworker without revealing anything confidential. I write about patterns and principles, never about specific employers, customers, or internal systems.

Beyond the writing#

Alongside the thinking, I build. The Work section covers two real, deployed offerings: custom website building for organizations that have outgrown template builders, and a nonprofit back-office platform that grew out of a live production system for a charity serving seniors and veterans. Both are proof that the principles here aren't theoretical — they ship.

If any of this resonates, the contact page is the front door. I'm always glad to compare notes with people who care about building systems other people can trust.