About the tutoring

This page is about how I work with students in tutoring—not a full biography. For career path, tools, and the longer story, see About Darko.

What I bring

I have spent over ten years in Unity and C# on real games: multiplayer, AR/VR, gameplay systems, tooling, and serious-game projects. I ship code, not just slides. In tutoring, that means I can meet you at the code and the architecture—where things break, where cost hides, and what to simplify first.

How I teach

I am direct. I will tell you when an approach is wrong for your project size, when you are over-engineering, and when the problem is fundamentals, not the latest feature. I repeat explanations until they stick, and I use your project as the classroom so the lesson sticks to something you care about.

I keep a small roster on purpose. Tutoring only works if I remember your codebase and your goals. If I take you on, you get attention—not a rotating cast of coaches reading a script.

What I expect from you

Show up with something concrete: a repo, a bug, a design you want to implement. If you are brand new, we still start from a concrete goal (for example, “I want to finish a small vertical slice”), not from “teach me everything.”

Next step

Read what we cover and how it works, then check the overview for the rate and booking status.