I build gameplay systems and tools that help take a feature from an early prototype to production-ready code. I translate design requirements into technical decisions around system logic, data structure, performance, and team workflows. The goal is not code that only works once, but implementation that stays readable, extendable, and resilient as the project changes.
My work can touch gameplay mechanics, tools, feature integration, optimization, system logic, technical infrastructure, or presentation-layer code. I am not interested in treating these as isolated boxes, because in a real game they usually meet inside the same feature.
Shipping projects on PC and consoles taught me to judge code by more than the first working version. A good implementation should support iteration, survive edge cases, remain debuggable, and make the next decision easier for the team.

