They do have advantages:
The issue I have with step-by-step tutorials is that they don't usually promote the programmer taking time to understand it, but rather encourages them to take shortcuts and simply copy and paste the code to get the game done. This leaves them running into the same issue until they stop and try to figure it out themselves or get guidance from another programmer who won't give them the answer right off. That is just my personal opinion on them though.
This is the exact problem I'm running into. I'm to a point where I can recognize someone's patterns, but they're still mum as to methodology.
I've been really hurting for guides that stop and explain the programming equivalents of "hey, if you're microwaving food, arrange it around the edges of the plate so it heats more evenly," or "yeah, you could drive that screw into the wall with a hammer, OR you could use a screwdriver because it works WITH the screw."
They do have advantages:
- They give beginners a good notion of all the required expertise when implementing a specific game
- They give a good insight on different ways of tackling different problems (different devs, different approaches to game dev)
- They give a good notion of what's required to implement a speicifc game design
The only ones that get that advantage are the ones who actually bother understanding the code in the tutorials. Unfortunately, the number of 'beginners' who are impatient and want to go from 0 to 60 now is steadily increasing.
So, the fault lies in part of the audience, not the author of the tutorial or the intended audience. This is a whole different discussion, and has nothing to do with people who enjoy reading tutorials with a specific purpose. Take the SFML book mentioned in this thread: not only the author gives a great insight into all the required expertise for creating a whole game, inspiring the reader to go the extra mile after reading the book, but it also gives great C++11 tips and game design tips. It's a wonderful book, impossible to get bored while reading. Now, how many programming/game dev books you slept while reading?
There is different content for different people. And some enjoy working on full projects, with clear objectives, and have a helping hand going through it all.
The only ones that get that advantage are the ones who actually bother understanding the code in the tutorials. Unfortunately, the number of 'beginners' who are impatient and want to go from 0 to 60 now is steadily increasing.They do have advantages:
- They give beginners a good notion of all the required expertise when implementing a specific game
- They give a good insight on different ways of tackling different problems (different devs, different approaches to game dev)
- They give a good notion of what's required to implement a speicifc game design
I always recommend books, never tutorials. Simple reason is that tutorials aren't as detailed as books on the same topics. If a book doesn't exist and a tutorial is your only option, then I would approach it with extreme skepticism.
They do have advantages:
- They give beginners a good notion of all the required expertise when implementing a specific game
- They give a good insight on different ways of tackling different problems (different devs, different approaches to game dev)
- They give a good notion of what's required to implement a speicifc game design
That is all with the assumption the tutorial is written by a person that actually knows what they are talking about. Then you also have to work on the assumption they cover everything without leaving out steps or vital information.
I just think it's wrong to say those tutorials/content is bad for a programmer then blame it soley on the users of the content that doesn't put the time and effort in.
Sorry, you are right. I shouldn't blame the tutorial for the lazy part of the audience. Instead I should focus on the fact that, as I stated, tutorials don't go into as much detail as books do. Depending on the writer, it may be erroneous in facts and details that are covered. I used to spend my days trying to help sites correct their tutorials, hoping to make them useful to beginners, but the things I ran into regularly were tutorials that promoted one or more of these: bad programming habits, bad programming styles, erroneous code, poor project layout, misuse of terms and jargon, misrepresented concepts, and advice that contradicted documentation or standards. So I'm anti-tutorial, pro-book, pro-mentor, and pro-team to learn.
If you want to collect tutorials then go ahead and find them, but as I said, be skeptical about them or run the risk of learning something that you may have to unlearn later.
I always recommend books, never tutorials. Simple reason is that tutorials aren't as detailed as books on the same topics. If a book doesn't exist and a tutorial is your only option, then I would approach it with extreme skepticism.
That is all with the assumption the tutorial is written by a person that actually knows what they are talking about. Then you also have to work on the assumption they cover everything without leaving out steps or vital information.They do have advantages:
- They give beginners a good notion of all the required expertise when implementing a specific game
- They give a good insight on different ways of tackling different problems (different devs, different approaches to game dev)
- They give a good notion of what's required to implement a speicifc game design
Sorry, you are right. I shouldn't blame the tutorial for the lazy part of the audience. Instead I should focus on the fact that, as I stated, tutorials don't go into as much detail as books do. Depending on the writer, it may be erroneous in facts and details that are covered. I used to spend my days trying to help sites correct their tutorials, hoping to make them useful to beginners, but the things I ran into regularly were tutorials that promoted one or more of these: bad programming habits, bad programming styles, erroneous code, poor project layout, misuse of terms and jargon, misrepresented concepts, and advice that contradicted documentation or standards. So I'm anti-tutorial, pro-book, pro-mentor, and pro-team to learn.I just think it's wrong to say those tutorials/content is bad for a programmer then blame it soley on the users of the content that doesn't put the time and effort in.
If you want to collect tutorials then go ahead and find them, but as I said, be skeptical about them or run the risk of learning something that you may have to unlearn later.
I'm currently working through this book to learn Game Development:
http://www.amazon.com/Game-Coding-Complete-Fourth-Edition/dp/1133776574
It's an excellent book which takes you through the basics of architecting a game, to writing the game and tools itself. The authors also update the code as people find issues with it, and respond to posts on their boards.
I heard bad comments about that book, but i'm not sure about the edition people were talking about. Does it give a good architecture overview? Is it standing the test of time?
Game Coding Complete ACCU Review: http://accu.org/index.php?module=bookreviews&func=search&rid=1724
Even on the Amazon.com link, the only 1 star review was by a guy, who reading his review, makes it sound like he was expecting a book that held his hand through the development process from beginning to end (his quote below).
I'm not sure why this book is so highly rated. It's a smattering of mostly useless information which does little to help one actually program games. It reads like a compilation of blog articles rather than a thoughtful and well organized progression of information. This was a true waste of money.
I enjoyed the book and its "smattering" of information. I also enjoyed SDL Game Development and SFML Game Development. That isn't saying much though as I also enjoyed reading Programming: Principles and Practice Using C++, C++ Primer, The C++ Standard Library, The C++ Programming Language, Microsoft's Code Complete, Programming Game AI by Example, Beginning COBOL for Programmers, etc., etc., etc. I may have little confidence in my abilities to program, but that doesn't take away from my joy of reading and learning about programming, game development, or other programming and web languages or to help others. I've got quite a large library, but outside of Game Coding Complete, SDL Game Development, and SFML Game Development most of them focus more on the C++ language, OpenGL, DirectX, or Game Engine architecture so, while I enjoyed reading them, I wouldn't recommend them for this thread. I think those three (GCC, SDLgd, and SFMLgd) are the best books for what you are looking for in the OP.
