I’m Stanley.

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 built 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

• an orchestrator that routes subtasks to different coding agentscheaper models for mechanical edits, stronger ones for design and review
• a triage pipeline that scores, tags and links product feedbackit replaced a gate that quietly created no issue at all for anything judged a duplicate
• VandyCV, an LLM-backed resume builderNext.js, Flask, PostgreSQL. I owned the backend, the schema and the prompting
• Klondike Solitaire, a production full-stack gameevery move stored with before and after state, so undo and replay came for free
• VR environments for the Wallace Lab at the Vanderbilt Kennedy CenterUnity and C#, eye tracking and binaural audio, inside a frame budget

Some things I’m into

• agent orchestration, and the question of which loops get to write
• developer tools that respect the person using them
• volleyball. I set, and we won an NCVF Division II national title in 2023
• teaching, which is still the fastest way I know to find out what I do not understand