VP of Engineering at Omada Health. Advisor at Berkeley SkyDeck.
I write about engineering leadership, distributed systems, AI/ML adoption, Ruby, Go, PostgreSQL, and open source. I’ve spent the last decade building and scaling engineering organizations in digital health.
Originally posted as a thread on X. I was reading that 8090 just landed a partnership with EY last week, and this got me interested in test-driving it. Most of the coverage out there focuses on enterprise usage, I wanted to know if it could help me on an open source project (no budget, PMs, just me/Claude/my repos.) And if this is good for thousands of consultants, maybe it could also be good for the day job. I’ll start by saying that I liked the pitch: the bottleneck in (a lot of, not all obviously) software is deciding what to build, not writing the code. 8090 wants to be the single source of truth that connects product decisions to engineering execution: a gap that’s more or less narrow in various companies, and that doesn’t exist in side projects (where I’m the CEO/CFO/engineer/QA/product marketing person all at once.) ...
This blog has been running Jekyll since 2014. It served me well for years, but the theme was showing its age, the tooling felt stuck, and I wanted something faster and more modern. So I migrated to Hugo. One theme per decade I guess. ...
Originally posted as a thread on X. I’ve been building AI agents for a while now and I’m a bit puzzled about where the industry is going. We’re writing the most autonomous software we’ve ever built, but the tools we use to build them are a mess. Python script calling APIs, state scattered everywhere, YAML configs, framework-of-the-week. It works until it doesn’t, and then you’re debugging at 2am because some MCP gateway is stuck as some tool or API changed shape and nothing caught it. ...
Originally posted as a thread on X. I’m building an agentic harness modeled on Elm’s architecture: a strict functional pipeline where untrusted agent code runs in total isolation. Containers felt like the natural security boundary. Apple’s open-source container tool seemed like the ideal foundation. Building and running containers is dead simple (container build . -t my-image, container run -it my-image), but I still spent a chunk of my weekend (re-)discovering what breaks when you try to get graphical output across a real VM boundary on macOS. ...