OOX Limited

Menu
get in touch

Srđan Radujko

Unity Developer
Srđan Radujko

Srđan Radujko is a Unity Developer within our game development team, specializing in mobile game development and real-time system implementation.

With a practical mindset and a focus on clean, maintainable code, he balances speed and structure in fast-paced production environments. His approach favors solving real problems efficiently while keeping systems understandable and adaptable.

SKILLS

  • Unity Development & C# Engineering
  • Game Design & Systems Thinking
  • Automation & Tooling (Developer Efficiency)
  • Project Leadership & Agile Management
  • Cross-Disciplinary Collaboration

PROGRAMS

  • Unity
  • Visual Studio
  • Mobile Profiling Tools
  • ChatGPT (wisely used)

Srđan Radujko

Unity Developer

Srđan Radujko is a Unity Developer within our game development team, specializing in mobile game development and real-time system implementation.

With a practical mindset and a focus on clean, maintainable code, he balances speed and structure in fast-paced production environments. His approach favors solving real problems efficiently while keeping systems understandable and adaptable.

Q&A

Accessibility. Unity was the first engine that came up when I googled “how to make a game.” It became a natural starting point, and over time, a professional focus.
It depends on the system. Building from scratch gives more freedom and control. But refining and improving an existing system has its own satisfaction. Optimization and clarity often come from iteration.
Traveling, visiting friends, going to band gigs, and playing music.
,,Nek bude borba neprestana.”
Bungee jumping (skydiving is next). First live show with a band. Being a best man to my best friend. First big trip. Yes, that’s four.
Old-school Fortran helped me understand the fundamentals of programming logic and object-oriented principles. The rest of my technical development came from self-learning, online resources, and hands-on experimentation.
Game jams. They taught me how to balance ambition with deadlines. Perfectionism can sabotage delivery, especially in fast-paced environments like game development. Shipping matters.
You don’t start with scalability. You build a system that solves the current problem. Scalability becomes relevant once the idea proves itself. Overengineering early can slow everything down in a rapid development cycle.
First, make it work. Then optimize once the game idea is validated. Premature optimization wastes time if the core concept doesn’t survive testing.
Break it down. Identify which system is responsible for which behavior. Testing components independently helps isolate problems. Logging and step-by-step validation reduce guesswork and speed up debugging.
Following principles like KISS and SOLID. Keeping systems readable and understandable for whoever has to work on them later. Clean code isn’t about being perfect. It’s about being understandable.
Game development is still product development. People think making games is just fun. It’s work like any other product-based industry. The difference is that the end result is entertainment.
Googling. Or now — “ChatGPT-ing.” But not copy-pasting blindly. Understanding why something works is more important than having code that compiles. Also, building small games from start to finish teaches more than endless tutorials. Going through the entire development cycle reveals how systems truly connect.
  • oox menu