“A sturdy model gives a strange idea somewhere solid to stand.”
Before the studio became the focus, I spent years working close to
operational data: SQL, ETL, partner integrations, reporting, metadata
systems, scheduling, file movement, APIs, and data-lake work. That
experience still shapes how I make games, even when players never see it.
It taught me to make rules explicit, track state carefully, test the
important paths, and build tools for the repetitive work around the
creative work. I use AI-assisted development in the same spirit: move
quickly through possibilities, then make the result understandable and reliable.
What carries over
Clear models, reliable state, useful automation, careful testing, and respect for the boring parts that keep a game alive.
The résumé version
Data engineering and integration leadership across healthcare and benefits systems. The detailed chronology lives on LinkedIn; this site keeps the focus on the studio.
Tools I reach for
Languages
- Python
- JavaScript
- TypeScript
- HTML
- CSS
Backend & Data
- FastAPI
- Flask
- Jinja2
- SQLAlchemy
- Alembic
- PostgreSQL
Quality & Delivery
- pytest
- Ruff
- mypy
- Docker
- Docker Compose
- Railway
- uv
Selected work on GitHub