Planning is key to achieve what you set out to do within a given budget. What are we going to build? How are we doing that, why, and how much time will that take? A crystal clear development plan answers all questions before developing and lays a path for prioritization.

I have multiple users in mind when I design experiences. The end user, who should be able to use the product intuitively. Plus anyone else who is part of the development cycle, from co-creators to stakeholders.

Audio provides a feel, a sonic addition that is engaging and informative. Great sound design is smooth - it enriches the story, rather than exposing a void when it is overlooked. Something that is visual, usually makes a sound, then it becomes alive. We take sound for granted in real life, so let's aim to make virtual worlds just as convincing.

Component-based architecture is one of the major strengths of Unity. I like to build generic and maintanable components. I stitch logic together using composition rather than over-inheritance. Ultimately reducing production time and creating something that's modular and maintainable.

I aim for a balance between flexibility and simplicity, ensuring code is easy to read, maintain, and extend. I use design patterns where needed. In that sense, my approach emphasizes scalability and long-term sustainability, supporting both immediate project goals and future development needs. I follow Unity's C# style guide for consistent code quality and appreciate code reviews as learning opportunities to improve my skills.