I came to engineering sideways. A medical degree, an MBA, and close to a decade leading QA and localization teams taught me how distributed teams actually function and where the friction really lives. The pattern I kept running into was the same one every time: the work was fine, the tools were the problem. So I started building small fixes, then bigger ones, then went full-stack — and eventually realized the thing I most wanted to build was the substrate itself.

Now I build products and run them: architecture, infrastructure, pricing, support, the lot. Before that, four-plus years shipping production software across health tech, IoT, and enterprise tools, mostly as the person responsible for the technical calls.

The thread running through the current batch is that software should be operable by whoever — or whatever — is doing the work. MailMatter hands an agent its own inbox over MCP. Projectyl exposes a team's work the same way. Tabler is getting the same treatment alongside analysis over aggregated booking data. A clean, documented surface serves all three: a person with an API key, a script running in CI, and an agent working on someone's behalf. They turn out to be the same requirement.