About

I build things at the intersection of artificial intelligence and developer tools. This page is a snapshot of what drives me, what I care about, and how I think about the work.

Philosophy

I believe the best tools disappear. The software worth building doesn't demand attention — it removes friction so quietly that people forget it's there. That conviction shapes everything I work on.

Most of the technology industry optimizes for engagement. I'm more interested in the opposite: building systems that help people spend less time in tools and more time in the work that matters to them. The measure of a great product isn't how long someone uses it — it's how quickly they achieve what they set out to do.

I also believe in building in public and thinking out loud. Writing is how I stress-test ideas. Shipping is how I stress-test intuition. Both are necessary, and neither is sufficient alone.

Interests & Expertise

The problems I gravitate toward sit at the seam between how people think and how software works. A few areas I keep returning to:

Context-Aware Agents

Building AI systems that understand the full picture — not just the prompt, but the intent, history, and surrounding constraints that shape what someone actually needs.

Developer Experience

The gap between what a developer intends and what they have to type is still too wide. I'm interested in tooling that closes that gap without adding new abstractions to learn.

Knowledge Systems

We generate more context than we can retain. I'm drawn to systems that capture, connect, and surface knowledge at the moment it's actually useful.

Static-First Architecture

I favor systems that are fast by default, predictable to deploy, and resilient to failure. Complexity should be earned, not inherited.

Background

I've spent my career founding and building software companies. The thread connecting all of it is a fascination with how people and systems work together — and a frustration with how much friction still exists in that relationship.

I started as an engineer, moved into product, and eventually into founding. Each step gave me a different lens on the same problem: the distance between having an idea and seeing it realized is still too large, and most of that distance is artificial.

Today I spend my time building tools that compress that distance — primarily through AI agents that understand engineering context deeply enough to act on it. When I'm not building, I'm writing about the patterns I notice and the questions I can't stop thinking about.

Principles I Build By

Ship, then refine
Working software teaches you more than planning documents. Get something real in front of people early.
Complexity must be earned
Every abstraction, service, and dependency should justify its existence. Default to the simpler path.
Tools should disappear
The best software is invisible. If someone has to think about the tool instead of the work, the tool has failed.

Interested in discussing this further?

I'm always open to connecting with fellow builders and founders.

Start a conversation