Architecture with a designer's eye.

I started as an artist — print design, then graphic design, then web design, back when "website designer" was still a job title on its own. Somewhere along the way I got curious about how the things I was designing actually worked, and that curiosity turned into a career. That path still shapes how I work: I approach systems with a designer's attention to structure, detail, and the people who will use them.

Fifteen-plus years in, I've built software for government, banks, health and pharma companies, utilities, and retailers you've heard of — and I still run Be Free Studios, the studio I started in 2004, on the side. These days that means painting and printmaking, freelance graphic design and brand identity work, and web design and development for clients who want both design sense and engineering behind their site. (There's also a woodshop making custom picture frames and trading card stands, if you're into things like that.)

Different medium, same instinct — figure out how something's built, then build it better.

Most of my work lives in the layer under the features: design tokens, component libraries, forms and data grids, and accessibility treated as a correctness constraint instead of a checklist. Lately I've been building the tooling that keeps a codebase honest — agent harnesses, pattern audits, shared vocabularies — so a team's judgment applies on every push, not just when the right reviewer happens to look. I like the hard, tangled problems where the first answer falls apart. Learn by building, not by title.