About
I like problems where the correct answer is a system, not a feature.
I've spent most of the last eight years building the infrastructure underneath other things: deployment platforms, queueing systems, identity integrations, and now AI infrastructure. The common thread isn't a specific technology, it's a preference for the layer that everything else depends on but nobody sees until it breaks.
I've built two developer-hosting platforms independently of each other, seven years apart. Forest, bootstrapped with two other engineers, reached real users and was acquired. Canopy Host is the second attempt, this time built alone, and this time with an actual point of view about what the first one got wrong.
I care more about a system being honest than a system looking impressive. Cortex refuses to answer when it doesn't have the evidence to back an answer up, on purpose, even though a confident wrong answer would demo better. That trade-off, correctness over polish, shows up in most of what I build.
Outside of the systems, there's writing, some of it technical, some of it not. It lives in the footer rather than up front, not because it matters less, but because this page has a job to do first.