Hacker News Reader

Comment by robmerki | Hacker News Reader

I've tried everything, but the only reliable way I've learned hard things is by diving straight in to something way over my head. Grinding through something with a dozen StackOverflow (or equivalent) tabs open is how I taught myself Javascript/React, HTML, Unreal Engine, and even Audacity. Note taking is probably "better", and I use spaced repetition if I have to memorize things, but the core method is just grinding on something I'm deeply interested in.

View on HN

I am similar but I cannot for the life of me understand game engine workflows. Other libraries and frameworks I get after a while of reading docs etc, but the workflow for game engines is so different than what I normally do that I get thrown off course lol. Any tips for unreal?

After spending a ton of time with React/Javascript/Html/CSS it worked in my brain like this: - Game logic is your Javascript - Animations/Models/Textures are your CSS - Game objects (i.e. the character you control, NPCs) are like React components - Levels/Maps are your "database"

Now that I've typed that out, it almost doesn't make much sense. But that's how it fit together in my brain.

I don't know about a engine workflow, but I was inspired to make a few games in JavaScript after reading the book/website http://gameprogrammingpatterns.com by Robert Nystrom

That helped me understand frame-tick/physics-tick aspect at least, and how you could offload some processing onto separate queues of events.

Reply on news.ycombinator.com