Open any project for the architecture and the decisions behind it.
Long-term memory, a 48-tool agent loop, and real-time voice, built on the Claude API. It reviews its own weak conversations and opens pull requests to improve its code, which I approve before they merge.
47 services in family production with single sign-on, encrypted secrets, immutable offsite backups, and full observability. I stress-tested it with an LLM-driven penetration test that surfaced a real CVSS 9.3 vulnerability.
A 2D simulation in Godot and C#, playable end to end. I scoped and shipped all 13 development phases in about four weeks, with a unit-test suite and CI, and produced a downloadable build.
I own the infrastructure and deployment for three products, build the internal tools our marketing team runs on, and built the MCP server that puts our CRM inside Claude.
A local-first LLM pentest agent driving an offensive-security model entirely on-device. No API keys, nothing leaves the machine.
A deployed web app for a tabletop campaign: player journals, a GM hub with maps and trackers, real-time shared state.
A fully local coding agent (stdlib-only Python) driving a 35B model on-device. Built to keep shipping when cloud AI was paused.
A fast, dependency-light marketing site delivered for a real advisory-firm client, deployed on Netlify.
An end-to-end ML prediction pipeline and a validated survey study analyzed with EFA, CFA, and SEM.
Engineering, teaching, research, and enterprise IT.
I build software end to end, across apps, infrastructure, AI systems, and data. I pick up new tools fast, use AI to move quickly, and like the whole range of the work rather than one narrow slice of it.
In the last year that meant a self-improving AI assistant on the Claude API, a 47-service self-hosted platform I hardened with an LLM-driven pentest, a 48,000-line game taken to a playable build, and ownership of the infrastructure and internal tooling behind an AI startup's site and CRM, including a production MCP server that connects Claude to that CRM. Different domains, one instinct: learn the tool, build the thing, make it survive real use.
The other half of me is a teacher. I taught 90+ students solo in an intro information-systems course, holding a 93% class exam average with no faculty oversight, and before that spent two years training and leading people, turning newcomers into confident, independent leaders. The work I care about most is not just building something that works, but making sure someone else can own it after I hand it off.
Email is the fastest way to reach me. Résumé and profiles are below.