Performance & graphics
Predictive loading, dynamic resolution, custom shaders and caching that keep games smooth on the weakest phones.
Engineering Lead · Agentic Development · Software Architecture
Finding talent in the dark is hard. Here's a light.
Profile
I'm a lead front-end engineer with 15+ years in software, drawn to architecture, systems design and hard problems. Most recently I led the front-end core systems behind a studio's high-end slot and crash games, and led its move to building with agents.
I direct the engineering while agents write most of the code, which lets me deliver like a small team without giving up clean, modular architecture. Self-taught; programming since I was 12.
What I bring
Predictive loading, dynamic resolution, custom shaders and caching that keep games smooth on the weakest phones.
Led a studio's move to building with agents: the practices, the agent skills and documentation, and core systems rebuilt to be agent-first.
Designed and wrote a games framework end to end; owned front-end systems design across three companies.
Work
Lead Front-end Engineer · MoonX · Nov 2024 – present
The front-end core behind high-end slot and crash games on PixiJS and Spine. I designed and wrote most of it, and the systems around it:
Senior JavaScript Engineer · impact.com · 2016 – 2019
Helped architect, build and maintain the reporting platform used by hundreds of thousands of active users, from single bloggers to dozens of blue-chip companies, and moved it off its legacy UI onto React, Redux and Redux-Saga.
Lead Front-end Engineer · A24 Group · 2019 – 2024
Led a remote team of five and the front-end of the company's messaging system: Twilio underneath, RxJS handling every part of the stream.
Games
Fast-paced isometric co-op for one to four players: gather herbs, brew spells at your cauldron, and combine spells to beat rival warlock factions. Godot and C#.
Co-op survival horror in a generated English town after the world has gone dark. Godot and C#, built almost entirely through agents.
How I build with agents
Several agents in parallel, each in its own git worktree, working from written specs, project rules and a binding decisions log, so later work doesn't undo earlier choices.
Review agents that didn't write the code check the architecture before anything is merged.
Tests and golden-master checks catch regressions, so the code stays clean and modular at a pace one developer couldn't reach alone.
Experience