Galaga5

Sure: Make games, not engines. To break it down a little more: come up with a game you want to make. Start making it. You'll figure out how to make an engine as you start making your game. To break it down even more: I wanted to impress an old girlfriend by making a clone of Galaga, cause she loved it as a kid. I decided to make Galaga in HTML5. I wanted to start by rendering the ship to the screen, so I went down that path until I could do it. How do I draw something to the screen on the web? Use Canvas - figure out how to reliably render a canvas element on the page and fill it a color. How do I draw an image? Draw sprites on the canvas - get a sprite of the ship then figure out how to draw it. How do I move the ship? Create a backing representation of the state of the game, then render the world based off that. I now have a simple game

I'm working through Unity tutorials now and this is what I did, and I'd agree. Being a web developer and knowing JavaScript is awesome for this - HTML5 games are really fun and easy. I started with a Galaga clone[1] that taught me about game loops, input, rendering, and the state of the game world and how they interact and are separate. I think this has made working through Unity, where things are kind of magical, much easier. 1. https://github.com/hoorayimhelping/Galaga5