top of page


So I understand this section is definitely veering towards blog territory rather than a Professional Portfolio, but adding "The Ray Tracer Challenge" to my website has really motivated me to talk about more books. For professional development, I feel its very important to keep learning...even if the topics are only tangentially related to your professional skillset! I love reading all kinds of books about  videogames: be it game history, programming, memoirs from industry veterans, etc. Even if I'm not learning anything new, a good book sure does pump me up to get into the office the next day and be a kickass Tech Artist!  One day I hope to get a book published to inspire others. I mean, it could happen haha. Anyway, please enjoy, oh and reach out to me about any videogame books that have motivated you!



Man, this book is SO captivating, I read through it twice! Chris Alaimo recommended the book to me when it released, and I'm so glad I purchased it. I read through the entire book in two days back in October 2020 while I was fighting an illness.  Now, I'm sad to say that I am a fraud:: I didn't grow up playing alot of Sierra Adventure games...heck I played more of the Brother Chaps's parody game "Peasant's Quest" then anything by Roberta Williams. But perhaps that's part of what made this book so compelling to me: I didnt know much about the history of Sierra On-Line. The book is a personal biography, company history, and a business guide book all rolled into one. The presentation is so good: all the ground it covers, with plenty of colored pictures to really help spark the images of the scenarios in your head!

I really love reading books, listening to podcasts etc that help me imagine what I might of been doing being born in a different time period. Ken goes into great detail about the early days of computing in college: working on mainframes, punch cards, and tele-type time sharing! The book has tons of photos and picture scans from the era. It really brings me into the 70s, and as the book goes on, the 80s and the 90s. Ken shares alot of personal, anecdotal stories living in Oakhurst, meeting celebrities, going from a mom-n-pop business to a videogame empire. Reading through, you know the chapters, you know the inevitable downfall is coming...but secretly hope the ending is actually somehow different!  Even just the standalone stories about individual games is very fun: from Mystery House (1980) to Donald Duck's Playground (1984) to Phantasmagoria (1995) it covers all kinds of ground in ~375 pages.

Throughout the book, there are several Interlude chapters where Ken tries to give "industry advice", up to and including how to manage time as a software developer. I feel these parts are ok, but they certainly do feel like Ken's game industry knowledge is somewhat frozen in the late 90s. Still, its great to hear his insights. So obviously, the book is from Ken's perspective, and he was fortunate to be at the top of the foodchain of Sierra, looking downward. Was he a good leader, did he step on folks along the way, did he deserve the success he was given? It's always good to listen to multiple perspectives of historical events to get the full picture. I'll say this though, the fact that Ken was a Software Engineer and that he and Roberta made Sierra On-line out of seemingly nothing, that reads like an inspiring story.  Please give it a read!



This is a great book to flip through when brainstorming just the right structures for a system you're going to be implementing. The book goes through fundamental design patterns that folks usually learn during our first coding and data structure classes. So, for seasoned programmers, don't expect  any groundbreaking paradigms or nothing. For me personally though, I really enjoy relearning concepts I'm already familiar with, especially told with a different, entertaining way.  And Robert Nystrom certainly makes the chapters fun to read! He's a seasoned gameplay programmer from Electronic Arts, who definitely seems to have game development war stories to tell! He even cites when these patterns were utilized during his career. For example, using Event Queues for Henry Hatsworth in the Puzzling Adventure. The book is very much written for C++ folks, although his sample code avoids using STL etc for the sake of making the code logic more agnostic.  I sure wish I had a book like this during my college days:  more accessible for would-be game developers than Scott Meyer's Effective C++ I would say!!

Each chapter in Game Programming Patterns is dedicated to one Pattern, and for the most-part standalone, citing similar patterns within the book with page numbers to easily follow the thread. Each chapter ends with bullet points citing which game engines or code languages have intrinsically utilized the Design Pattern for further real world references too. The book has great illustrations to help visualize data, flow, etc (along with pictures of pirates on masts to demonstrate transform-spaces ).  Some of Nystrom's analogies kill me! For example, in explaining Data Locality, he describes a scenario where "you" are an accountant, in a tiny little office who is forced to rely on a "warehouse guy" to fetch data for you with his box at a time. This story is to help illustrate memory access speeds...contrived yes, but I love these parts of the book!

The book is a spiritual sequel of sorts to the "Gang of Four's" Design Patterns (1994) and the first third of Game Programming Patterns revisits key patterns from 1994 with the specific lens of "modern" game development.  Well, actually this book was first released in 2014, so it's not quite modern anymore. Multi-threaded job tasking for the new game consoles, multiple-skew mobile development, and "Has-A" Component-Based systems were the hot-newness when Nystrom was authoring the book. Speaking from a Tech Artist's limited perspective, the book is still relevant to modern development through and through.

Like I said at the start, I think Game Programming Patterns works great as an "office-table book" that you flip through when thinking about how to refactor your data structure to be more efficient etc. Alot of the chapters are painfully 101, but yet I still enjoy reading through them as a refresher. Yeah, I really didn't learn much from the 'Double Buffer' or 'Game Loop' chapters etc, but I still feel good reading through them. I especially loved reading his Bytecode chapter...which he spun off into a book called: Crafting Interpreters which I would love to walk through at some point!

bottom of page