Software engineer with 10+ years building data systems, multi-tenant platforms, and developer tools in Python, Go, and TypeScript. Currently lead engineer on a multi-tenant SaaS platform - owning architecture and end-to-end delivery from Postgres schemas and CI pipelines through React frontends. Author of xpr-lang, a sandboxed cross-runtime expression language with byte-identical implementations in TypeScript, Python, and Go, shipped to npm, PyPI, and Go modules.

What I work on

Day-to-day I lead engineering at BengalByte on a multi-tenant SaaS platform - end-to-end across the Python/FastAPI backend, Next.js + React 19 frontend, self-hosted observability, and the deployment pipeline that ties it together.

On the side, I design and ship developer tools. xpr-lang is a sandboxed expression language with byte-identical runtimes in TypeScript, Python, and Go - I started it because every data pipeline I've worked on has wanted "a tiny safe expression language" and ended up with eval() or worse. restless, envdiff, and ports are small Go TUI tools I built to scratch very specific itches and now use daily.

How I think

• Problem first, tech second. The instinct to reach for a new framework is almost always wrong; the framework you already use will usually work.
• Owned end-to-end. Features are best carried by people who can take them from schema migration through frontend polish, then watch the deploy in Grafana.
• Leverage beats heroics. Conventions, code review, and good docs make the whole team faster - that's the job, not being the fastest person in the repo.
• Simple beats clever. If a junior engineer can't read the code in a week, I wrote it wrong.
• Backwards compatibility is a feature. Especially for content people don't realize is "data."

Outside code

Family time with my son, books on history and politics, and the ongoing quest to find a usable terminal HTTP client (which is how restless happened).