Beginning Game Programming, Third Edition Book

Jonathan Harbour, Beginning Game Programming (Thompson, 2005)

Beginning Game Programming has been kind of the holy grail of programming books for me for years. I can't even remember how it got such stature in my head, but over the last year or two it became one of the books at the very top of my wish list. When I found a copy for sale (relatively) cheap earlier this year, then, I jumped on it. Unfortunately, I had hyped it up so much in my head some disappointment was likely inevitable, but I tried to keep as even-keeled as possible when thinking about what to put in this review. After all, it's not a bad book, I've just read a number of intro-to-game-programming books that are better in at least one sense (comprehensiveness, readability, number/length/quality of code samples, or what have you).

One of the oddities of the book, and one which a number of novices will likely appreciate, is that the book focuses on C, rather than one of the more popular languages featured in books of this sort (C++, C#, or VB). For someone experienced in one of the other languages, that can be either a blessing or a curse, so take it into consideration. Aside from that, however, the main thing to note here is that the book dives right into game programming in C and DirectX (which version will depend on which version of the book you're reading; my copy is first edition, not second, and so the book's examples use an older version of DirectX than currently advertised). Code examples and discussions on the theory of game design start right up in the first chapter. Once again, this is something that some readers will find a strong point, while it will be a drawback to others. There's something to be said for some overview and nuts-and-bolts stuff (at least one of the book's reviewers complains about the lack of instructions for installing the software that comes with the book, for example), but if you kick things off from page one, you have room to cover more material in the same number of pages than you otherwise would. Can't call that a bad thing under any circumstances.

The book is also very small for this type of thing, only 337 pages, which limits the amount of space there is to cover material. Once again, something that could be seen by different readers as a good (not as imposing as doorstop-sized tomes) or a bad (not room to go into anything in depth) thing.

So, basically, it's up to you and what you're looking for in an intro-to-game-programming book. This could be it. It might not be. Check it out before shelling out the dough. ***