Skip to main content

Book Review: Game Programming Patterns by Robert Nystrom

I have started reading this book in December of 2013 when it was still in progress. Probably I have stumbled upon it somewhere on GameDev.js Facebook Group but I cannot really remember how I found it, but important point is that this time I have read it from cover to cover all over again to feel the difference with finished book.

The good thing about this book is that it is available both on paper and for free if you want to read it online. Just go to

I really liked the book and the hand drawn illustrations that really help understand the ideas. Best thing is that the author tries to emphasize how dangerous those patterns can be and many times warns the reader to do not use them if not needed. In my opinion having a list of downsides and pros of each pattern in one place that you can easily check in the browser, is really handy.

I have no idea if I am ever going to use any of them but having understanding of the underlying ideas behind for example Quadtrees can be useful if I am ever going to use it.

This book is for sure not only for game developers as many of those patterns are used in all kinds of applications. Other to be understood are coupled with descriptions of common problems, for example, how memory partitioning works or how you can implement your own language.  

Rating: 10/10


Popular posts from this blog

Course Review: The Bitfountain iOS 8 with Swift Immersive

This is second big iOS learning project. For first one read iOS Programming book review. As I only have two of them done I have to compare them somehow.

I am mindful that it took me a really long time to finish it (since last autumn). For a couple of months this year I didn't even have the internet to learn it, so it could not be helped. But last half of the June I've spent watching the videos every day and managed to finish it before any new internet problems.

So how was it?
In my opinion, it's great if you're starting out. There are a lot of basics, and seeing how to do things in XCode just makes your learning much easier than looking at the photos in the book. On the other hand, learning is more shallow and it is much easier to just follow the videos and learn only the basics without bigger picture about iOS SDK. I somehow missed more challenging exercises (even though I don't like to do them ;)

Course it pretty long but many videos are quite short (1-2…

How to Learn when Life is Short

I haven't really think this through but I have read really interesting articles recently and I just wanted to write for myself later.

Life is Short by Paul Graham

It's just that, learn from people older that you what is most important, and that life actually is short...

Instead of Goals or Resolutions, Try Creating Rules by Leo Babuta

In the time of New Year Resolutions, it's good to read something that is proposing different way of achieving things. Still I see much more value in habits than setting goals. But...

The Easy Way To Learn Hard Stuff by Per Harald Borgen
It's something that I read from time to time and I know it works sometimes for me. The things I learn then are really learned and something Jakub Wasilewski  has told me many times to do. Still it's uncomfortable and for some reason, I have failed to use this method more than once or twice. Writing it here so maybe I can think about it more and figure out how to do that more often.

Towards an understandin…

Hero's Journey in Presentations

Artur Skowroński recommended me: Want a Better Pitch? Watch This. by Andy Raskin and I think it is so great and applicable to all kinds of talks that I want to help it get more popular.
So the plan of presentation is going to follow these steps: Enemy - ProblemWhy now? - call to actionShow how the world will look like without the problemProblemsEvidence that you fixed the problem The image at the top is because it reminds me of Hero's Jurney. It has fewer steps but there is a lot of similarities. Especially #3 made me realize that grand vision of the future is something that I should have used in my talks.  The result at the start of the presentation makes a lot of sense actually. Everyone already knows that I speak about something because I probably fixed it and if you tell about it at the end then it might be hard for some people to see the bigger picture in the solution you're going to present.