I’ve made a lot of tutorials—well over 100—and some of them did surprisingly well for super niche game dev topics. So when I say “you probably shouldn’t watch tutorials,” I’m not doing the classic anti-tutorial hot take from someone who never taught anything. What I’m really talking about is the trap I keep seeing: people start with “I’ll use this tutorial to learn X,” and it silently turns into “I watch tutorials” as the whole activity. At that point, tutorials stop being a tool and start being procrastination that feels productive. The core idea is: your goal shouldn’t be “learn Unreal Engine” (that’s basically infinite). Your goal should be “make a small FPS prototype in a few months” or something similarly specific and achievable. Use tutorials only when you’re stuck at a point that’s genuinely too expensive to brute-force alone—like your very first intro to the UI, or a hard system you can’t untangle yet. My preferred loop is: set a clear goal, try it yourself, fail (a lot), read the documentation first, and only then grab a tutorial to unblock you. That failure is not wasted time—it’s what creates the mental hooks that make the correct solution actually stick.