I develop
I program gameplay, tools, saved state, and interfaces.
Ideas · shaped · shipped
I’m Clay—a student programmer, engineer, and team lead. I turn curious questions into working systems, then document what broke, what changed, and what I learned.
I’m documenting the projects I build and what I learn from them.

How I work
I know programming is only one part of shipping. I plan systems, build interfaces, test assumptions, and keep teams aligned when the project gets messy.
I program gameplay, tools, saved state, and interfaces.
I turn rough requirements into systems people can understand.
I debug what feels wrong and learn from testing the real build.
I divide the work, integrate contributions, and keep deadlines real.
My work
I use these case studies to show what I made, how it works, what went wrong, and what I would change next time.

Game development / leadership
I led the team and programmed a platformer mixed with a colony-management game.
See how I built it →
Game systems
I turned one line-drawing mechanic into five different local multiplayer sports.
See how I built it →
Embedded hardware
I built a working scorekeeper, soldered the electronics, and designed its enclosure.
See how I built it →
Apple platforms
I made my class schedule available on my iPhone, Apple Watch, and watch widget.
See how I built it →
Physics simulation
I wrote an n-body gravity simulation and made it interactive inside Unity.
See how I built it →
Product design
I designed a smaller, easier way to store and set up the entire board game.
See how I designed it →About me
I build games, apps, electronics, simulations, and anything else that gives me a reason to learn something new. I’ve also led a team in Italian and competed as a physics specialist, which taught me that engineering depends just as much on communication as it does on code.