Game Programming Interview Questions in 20 Minutes (Coffee Break Series)

Outstanding. I kept finding reasons to come back to it.

There is a particular kind of technical book that is dense without being difficult, and this is one of them. There is a section near the end that ties several earlier ideas together in a way I had not seen before. The progression from chapter to chapter is well thought out; nothing feels out of order. The examples are small enough to type out and experiment with, which is exactly what I want from a book like this. If you have the prerequisites, this is an easy recommendation. I will be keeping it on my desk rather than the shelf.

Mixed feelings. The good parts are genuinely good; the rest is forgettable.

This is the third book I have read on game programming this year, and it is comfortably the best of them. The exercises at the end of each chapter are worth doing — they caught a few misconceptions I did not know I had. The author is unusually honest about where the simplifications break down, which I appreciated. Fine, but there are stronger books on the same subject if you look around.

A useful guide. The examples assume a particular environment, but that is fixable.

This is the third book I have read on game programming this year, and it is comfortably the best of them. Some of the diagrams are dense and I had to reread a few sections, though that may just be me. The writing is direct and does not waste space on filler, which I value in a technical book. It is denser than the page count suggests, and I found myself slowing down around the middle. Four stars, and I suspect a second edition could easily push it to five.