[pooloo1]

Casey goes through the math, programming, and the logical processes of understanding how to build a an engine and a game with that engine. Its extremely deep, and extremely thorough, but it is by far the most extensive and explicit resource on the topic to date.

[bikitan]

"Extremely deep" is an understatement. It's long, deep and plodding enough as to be completely inaccessible to any but the most dedicated, and you have to be willing to spend hundreds, if not thousands of hours by the time it's over, going through it.

I love and appreciate what he's trying to do, but it's overkill.

[thorin]

It's definitely not overkill, it's probably one of the biggest free gifts to programmers I'm aware of. That said it would be a full time job for me for a year to get through it. I wish it had been available when I was a teenager and seemed to have infinite time on my hands.

[reificator]

On the contrary, the market is flooded with quick, easy tutorials with the (sometimes implied) disclaimer that it's not production ready. To have just a single example of the opposite is wonderful.

[chii]

There's no shortcut to mastery. Following Casey's will get you half way there, much more so than the many quick "tutorials" you'll find elsewhere.

[psyc]

Yes, you do have to be willing to spend thousands of hours to become that kind of game programmer.