Senior full-stack engineerGames to product to teachingNow building across web and filmBased in AtlantaOpen to senior roles

The brief

Videodrome is a physical video store in Atlanta with a catalog most streaming services cannot match: roughly thirty thousand titles, curated and organized by director and country rather than by algorithm. The job was to give that catalog a web presence worthy of the shelves, and to make the inventory behind it something the staff could actually run.

The hard part

The existing data lived in a legacy Clarion desktop database: a closed, decades-old system that was never meant to talk to the web. The real work was not the storefront, it was getting thirty thousand records out of that system without losing the hand-built organization that makes the store what it is, then modeling them in PostgreSQL in a way that supports search by title, director, and country, plus live rental availability.

The build

The front end is a TypeScript and Next.js storefront over that Postgres catalog: a fast search, filters for availability and genre, and film cards that show poster, director, year, and how many copies are left. The same data model feeds the point-of-sale and inventory side, so what a customer sees online and what the staff sees at the counter come from one source of truth rather than two systems drifting apart. The look is deliberately editorial and dark, built on a small design system so new sections stay consistent as the catalog grows.

Where it stands

The design and data model are built and the rebuild is in development, not yet live on the store's domain. The screens here are from the working design. Next up is finishing the migration tooling and the staff-facing inventory views before launch.

The brief

Bon House is an Atlanta venue building an audience, and it needed a web presence that matched the room: confident, quiet, and quick. The work was the front of house online, a site that sets a tone before anyone walks in.

The build

A TypeScript and Next.js site on a small design system, so events, listings, and new sections can be added without the layout drifting. The priorities were a fast first paint, clean typography, and a structure the venue can keep current without a developer in the loop for every change.

Notes

This is a client engagement. The screens and any brand assets are shown only where the agreements allow, so this page describes the work rather than reproducing it. Copy and assets here are a placeholder pending review.

The brief

For six years I was the lead instructor for a full-stack program, running cohorts of fifteen-plus students at a time. The harder, more interesting job came later: a full overhaul of the curriculum itself, treating it as a system with inputs, feedback, and outcomes rather than a static syllabus.

What I built

The overhaul modernized the whole stack a student moves through. It added AI and LangChain, moved core material onto TypeScript, introduced CI/CD and test-driven development as habits rather than topics, and added a Python module. The goal was a curriculum that compiles, in the sense that the path from day one to a shippable project is tested, current, and repeatable across instructors and cohorts.

Why it belongs here

Directing a program and re-architecting its curriculum is systems work and team direction, not a detour from engineering. It is where I learned to design something that has to keep working when many different people run it.

The brief

Two jobs, one theme. The first was a templated application built with Horton's senior developer on Angular and KeystoneJS, designed so the team could re-skin it for future clients instead of rebuilding from scratch each time. The second was a remediation: taking a bloated WordPress site (Sisters on the Fly) back to a state someone could actually maintain.

The work

On the platform, the interesting decisions were about the seams: what to make configurable, what to keep fixed, and how to keep a single codebase serving many client skins without forking. On the remediation, it was triage and discipline, cutting accumulated weight without breaking what the site needed to keep doing.

Why it belongs here

Designing for reuse and rescuing a system that has drifted are both senior signals. Most of the value was in the architecture, not the surface, which is why this is described rather than shown.

The brief

Before the web, there were games. Punchy Fox was the studio attempt, built with my longtime collaborator Tyler Aldridge, and the game jams around it were where I learned to ship something playable on a deadline. This is the start of the line that runs through everything else here.

The work

Punchy Fox reached a playable prototype before going on hiatus. Around it came jam pieces: "Is Anyone Out There?", which did well at its jam, and "La Bomba", a Bomberman-style clone that got to a working prototype. Game jams teach scope and finish in a way little else does, and that habit carried straight into building for the web.

Why it belongs here

It is the honest origin beat, and the bridge from this work sequence into the lab, where the more openly creative projects live. Demo footage exists and will land here once it is cleared with collaborators.