By learning from a tutorial over time, you'll attain some level of mastery (i mean, after seeing how every recipe tells you similar things, you have to learn it). But i think learning from a master like an apprentice is the much easier, and sure fire way to attain mastery.
Does anyone know about the depth and structure of the code in "How to Make an RPG"? From the post, it looks like it is focusing specifically on gameplay issues. Handmade Hero is covering quite a range of topics from basic gamepad input and audio output (done early in the series) on up. It is structured so that it's relatively easy to port to non-Windows OS's, and I like the live-coding feature which really shortens the code-compile-test cycle.
I guess it would be nice to see the table of contents and maybe a sample chapter or excerpts.
I bought the book. Haven't read it yet but the PDF is 978 pages and the downloads of source/assets was approx. 2GB.
Roughly glancing through the book, there seems to be code examples on most pages. Looks like he's using LUA.
Not even close. I think he spent the last three or four episodes working out how to efficiently sort sprites or something.
My biggest complaint is that he spends a lot of time setting up his dev environment that I found to be super confusing for a newcomer. I am an experienced dev and couldn't understand why he spent so much time mucking around with writing batch files and setting up emacs instead of just encouraging new users to just use Visual Studio where you can click compile and run and the setup takes 5 minutes instead of 2 screencasts.