A note on the framing.

The labels I could have picked all leave something out. Designer is too narrow when the design has to be built. Engineer is too narrow when the engineering has to be designed. Multi-hyphenate is honest but vague. So: solver complex.

A solver complex isn’t a discipline. It’s a posture. The instinct to look at a problem and ask, what’s the thing that would actually move this, and is anyone in the room going to build it. If the answer is no, you build it.

That posture shows up everywhere I work. A customs brokerage on a dying AS/400 system needed a CRM, so I built one and saved them $1.2M in licensing. My mother needed a calmer way to be reminded she’s loved, so I built her an iPad app. A musical needed 75+ projection cues run from a tool that didn’t exist yet, so I built that too.

TaskQueue was the earliest version of this for me, and the first time I built a shipped product end-to-end with AI as a development partner. One active task at a time, no categories, no tags, a constraint dressed up as a product. The constraint came from how I actually wanted to work. The shipping speed came from working with AI on the parts of the build I would have spent weeks on otherwise. That combination, opinionated design plus AI-accelerated execution, is most of what I do now.

Each problem looked like it belonged to a different field. None of them did. They all belonged to whoever would actually solve them.

This site is the long form of that pattern. Case studies are where the work lives. News is where the recent work shows up.