About me
I build tooling for coding agents.
I studied Computer Science and Human & Organizational Development at Vanderbilt, and I was the founding engineer at Handled AI in Brooklyn, where I designed an orchestrator that split engineering tickets into subtasks and routed each one to a coding agent based on what the work needed.
Most of what I have learned since is about boundaries. The agent loops that stayed reliable were the ones where I drew a hard line around what the agent was allowed to touch. The ones I trusted to stay in their lane did not.
Before that I taught Programming Languages to 150+ students a semester, built VR environments for a neuroscience lab, and ran production on a game studio’s internal FPS title.
Things I’ve built
all projects →Cheaper models handled mechanical edits, stronger ones handled design and review.
It replaced a gate that quietly created no issue at all for anything judged a duplicate.
A 5-person team project — I set up the repo and built the CI/CD pipeline.
Latest thoughts
all thoughts →- What if we had AI in groupchats?
Not a smarter assistant for one person. Something that actually sits inside the group.
- The question of which loops get to write
Read access is cheap. Write access is the whole design problem.
- Tools that respect the person using them
Most developer tools are built for the tool's convenience, not the person holding it.
Off the clock
- *Volleyball. I was the starting setter on Vanderbilt Men's Club Volleyball, and we won the 2023 NCVF Division II national title
- *Photography. Looking to travel to Banff and New Zealand next to take some amazing photos