I've been coding for a long time, and have long since wanted to make games. Nowadays the problem is creating a code base that runs on most platforms, is flexible and performant and not a nightmare to debug.
I love this series. I think it's great Casey is sharing his knowledge with us. But because he is making a specific game (and not showing how to make ANY game) there is a lot in there I won't need.
The game I'm trying to make with a friend is not tile-based. So it's hard to cut out which elements I need and skipping ahead to the ones I do.
Also, multiplatform is important. The first dozen videos are excellent since they show you how to do that, splitting out code for the windows platform and the game code, but it doesn't show how to go to the other platforms (linux, mac, android, ios).
I guess what I'm saying is - there is a lot of incredible knowledge in this series but it's hard for someone who wants to learn how to make games to use it for their own purposes. The first few weeks are brilliant and all new game coders should watch them, but then the series becomes specific since the aim is "this is how you can make A GAME" and not "these are the issues for making GAMES".
Anyway. I don't know if others have the same sense when going through these videos. I'm incredibly appreciative of Casey for doing this. I'd love to sort of be able to summarise everything, break it down into layers, and give people a piece-meal way of writing THEIR games from scratch with all the various things Casey shows us ...
Just a thought.