I treat prototypes as learning tools. I build the minimal version of an idea first, test it in context, and iterate quickly based on what’s works! delivering a playable loop as early as possible enables faster feedback from designers and stakeholders.

I strive to write code that’s both simple and adaptable - clean enough to read at a glance, yet structured to scale as projects evolve. I apply design patterns thoughtfully, prioritizing maintainability and long-term sustainability alongside short-term goals. Even under tight timelines, I favour component-based design and ScriptableObjects to keep systems decoupled. This keeps codebases flexible and makes swapping ideas in and out frictionless.

All prototypes are structured to be readable and understandable by others. I document key decisions, keep naming consistent, and avoid single-developer shortcuts that slow teams down. I follow Unity’s C# style conventions for consistency, and I treat code reviews as opportunities to sharpen my skills and contribute to better team practices.

I'm committed to continually expanding my skills through hands-on projects, code reviews, and staying current with evolving game development practices and tools.

I aim to create “Ah, of course, that makes sense!” moments, experiences that go beyond just functional and feel intuitive, satisfying, and easy to grasp. I test early and often, using player feedback to guide iterations and ensure every interaction feels playful, purposeful, and clear.

I use/build tools to streamline workflows and reduce friction wherever possible. Whether it’s a level setup shortcut, automated data generation, or debug toggles, I make iteration faster and remove repetition for myself and the team.