Development Skill
Code
C# · Python · Blueprints
I started coding out of curiosity, not from a course or a tutorial. I wanted to understand how games worked at the level where decisions actually happen. So I built one from scratch to find out.
How It Started
My first complete project was a fishing simulator, written in Python with no engine and no editor. Just code, a problem to solve, and enough stubbornness to finish it. The game had a full loop: cast mechanics, a fish catalogue, upgrade systems, and a resource economy, all written by hand. It was not elegant. But it worked, and it taught me how systems connect when there is no framework doing the work for you.
Building without tools forces a kind of understanding you cannot shortcut. Every loop, every state machine, every decision tree had to exist because I put it there. That foundation has shaped how I approach code in every project since.
Expanding the Toolkit
From Python I moved into C# and Unreal Blueprints. Visual scripting gave me speed and iteration flexibility in early prototyping stages. Written code gave me precision where performance and control mattered. Over four years of shipping in Unreal Engine I developed a feel for which tool to reach for and when.
Across projects
[NDA Project]: Combat systems, class prototypes, and abilities in C#.
Rivertale: Communication layer between custom Arduino hardware and Unreal Engine in C++, predictive interception projectile logic in blueprints.
Mowdown: Character rotation interpolation and respawn location system in blueprints.
Code as a Design Tool
My code work is always in service of design. I write systems that other designers can tune and extend without reading the source. Exposed variables, clear naming, and structure that communicates intent are non-negotiable.
Code that only the author understands is a design problem. A system that locks out the rest of the team creates bottlenecks, slows iteration, and breaks when I am not in the room. I write for the team, not for myself.