← Back to Home

Development Skill

Code

C# · Python · Blueprints · C++

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 my first game in Unity to build an understanding of it.

How It Started

My first complete project was a puzzle RPG, made in Unity for a minor in game design (2020). If I wanted to create something in Unity all I had was code, so I started with a simple moving platform. After this I started reading through programmer's code to get myself to understand more. This evolved into an understanding of scripting and a scalable way of coding.

C# code snippet
C# - Unity

Expanding the Toolkit

From C# I moved into Unreal Blueprints and Python scripts. Visual scripting gave me speed and iteration flexibility in early prototyping stages. Written code gave me an understanding of code structure and efficient coding. Over four years of working in Unreal Engine I developed a feel for which syntax to use.

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 simple 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 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.