Tomorrow, and Tomorrow, and Tomorrow

Tomorrow, and Tomorrow, and Tomorrow is a really well written novel. Telling a story of 2 childhood friends, Sam and Sadie, reuniting to develop games together, which eventually launches them into a world of fame, business and opportunities but also hatred, dilemmas and rivalry. The character development of these two, their family and their friends is really superb, it's definitely one of the strongest aspects. There are a lot of references to games of the era and gaming culture in general. The only thing that didn't quite meet my expectations is how the actual process of developing games is a bit unrealistic and often just glossed over. While the first game that the duo makes is explained in detail, the next games just mostly happen in the background while the drama takes the stage, which for me feels like a missed opportunity, even though a typical reader might not be interested in that aspect.

The book delves into the intricate dynamics of a crew of programmers who are immersed in the world of creating video games. It particularly focuses on the captivating relationship between Sam and Sadie, whose unique creative partnership stands out amidst a landscape dominated by romantic entanglements. There is an interesting exploration of the emotional world of the protagonists, which adds depth and intrigue to the narrative.

One notable aspect of the book is its inclusion of thought-provoking quotes. For instance, the line, 'Long relationships may be richer, but relatively brief and relatively short encounters can also be lovely. Not every person you know or love has to consume you to be worthwhile,' resonates with its insight into the nature of human connections. Another gem, 'Programmer: diviner of possible outcomes; seer of unseen worlds,' beautifully captures the essence of the protagonists' work and their ability to envision new possibilities.

The author does a commendable job in presenting a wide range of themes, spanning from the exploration of PTSD and amputation to the complexities of love and the intricacies of the business world. The book approaches these subjects with kindness and understanding, creating a sense of empathy within the reader. However, one area where the story could benefit from improvement is the handling of subculture references. At times, these references can feel heavy-handed and forced, distracting from the overall narrative flow.

While the book succeeds in presenting a mosaic of small encounters and diverse interactions, it may lack a clear overarching theme or structure. The narrative seems to meander without a definitive focus, which might leave some readers longing for a more cohesive storyline. Yet, this meandering quality also lends the book an intriguing sense of timelessness, akin to the famous line from Macbeth, 'Tomorrow and tomorrow and tomorrow...' The relaxed and mellow ending brings the story full circle, offering a positive outlook reminiscent of Shakespeare's tragedy but with a different perspective.

Overall, the book about the programmers' relationship and creative journey is a thought-provoking and compassionate exploration of human connections. While the heavy-handed references to subculture can occasionally disrupt the flow, the book's poignant quotes and empathetic portrayal of a diverse range of topics make it a worthwhile read. The relaxed and reflective ending adds a touch of closure, leaving readers with a sense of satisfaction.

At it's best moments, this book does a really great job of being both about games and evoking the if-then logic of games and game decision points. It also has interesting stuff about game engines (how they shape and constrain creation) and collaboration (the Jobs+Woz dynamic of a salesperson and a designer). It also feels like it was written for late Gen-X or early Millenials - references to Donkey Kong, Oregon Trail, Everquest, etc.

I think I would've liked it more if it were shorter...I liked the first half much better than the second, and some of that is because the latter half ends up pulling in mass shootings and 9-11 in a way that didn't feel like it connected with the core of the novel.

I should add that I listened to this, and I do think reading it would provide even more of that if-then logic. It's hard to pay close attention to structure (the book does some interesting stuff with chapter titles and branching logics at one point that doesn't translate as well in an audiobook).