More posts

Blood, Sweat, and Pixels by Jason Schreier

17 March 2021 (a year ago)🏷️ #100daystooffload🏷️ #book

💯 100 Days to Offload

This article is one of a series of posts I have written for the 100 Days to Offload challenge . Disclaimer: The challenge focuses on writing frequency rather than quality, and so posts may not always be fully planned out!

View other articles in this series

📚 This article is about a book

A quick warning: I always try to avoid giving away spoilers but be careful if you're worried about finding out too much.

🕰️ This is an old post

Please note that this article was posted quite a while ago and may now be out-of-date or inaccurate.

This post contains some of my thoughts on the book Blood, Sweat, and Pixels by Jason Schreier.

Blood, Sweat, and Pixels book cover

This book contains a number of stories about how some of the most well-known (and other less well-known) video games are made. The book's subtitle, "The Triumphant, Turbulent Stories Behind How Video Games Are Made", sums it up pretty well.

Working in the software industry myself, I often hear about the notion of "crunch time", which is a term we've borrowed from the game devleopment industry at times when critical updates, fixes, or deadlines are pressing. However, after reflecting on the stories in this book, it makes me realise that the "crunches" we suffer are nothing to the crunch and stresses experienced by game developers in many small teams and large development studios alike.

Every chapter explains in detail the pain and reward faced by game developers and management teams on an ongoing basis. The developer skill and expertise required by game studios, and the time and size of the required resource, helps to explain the huge financial impact these projects have.

It's no wonder why such harsh deadlines are set. In many cases it's a matter of "life or death": either the game gets released on time or there is no game at all and everyone has to lose their job - even in large well-funded companies.

I loved the stories of the groups of developers that ended up leaving their well-paid (but stressful) jobs in order to start something by themselves as a smaller group - not quite realising at the start what they were letting themselves in for.

I enjoyed the story behind the development of the game Stardew Valley. This is a game I love and have played for hours on my Switch - not knowing really (or fully appreciating) where the game came from and all the time spent by its solo developer and the stress that went on behind the scenes.

The background to the development of The Witcher 3 was also fascinating; how the relatively small but super-ambitious studio CD Projekt Red successfully brought to the world stage the Polish much-loved fantasy world.

The book was great, and well-narrated by Ray Chase (I listened to the Audible version). I only wish there were more stories (it only took a few days to get through), but I appreciate the effort the author went into with researching and interviewing some of the key people involved. It is an excellent insight into how parts of the game industry work.

📚 Do you use Goodreads?

If you're interested in seeing what else I read you can check out my Goodreads profile.

📲 Enjoyed this article? Subscribe to updates!

If you would like to read more posts like this, then you can subscribe via RSS.

Subscribe to an RSS feed