Game Programming Patterns (2014)
I had a bit of difficulty with this book. Loved reading it in every way (style, content, clarity, etc.) - but in parts[0] of every section I found myself thinking, &quot;wait - of course that&#x27;s what I&#x27;d do... but that&#x27;s just, like, the thing to do... why is it a pattern? Does it really matter if I call it that pattern or if I don&#x27;t know the pattern name?&quot;<p>Maybe it&#x27;s because I didn&#x27;t learn coding in university, or because most of my career has been spent in <i>very</i> small teams with little need to use pre-established jargon, but I get slightly annoyed when I see discussions about this pattern or that pattern and I have no clue what they&#x27;re doing, even if I&#x27;ve myself used that &quot;pattern&quot; dozens of times without knowing the accepted name for it. YMMV<p>[0] the other parts would be when it got into the nitty gritty of solving a specific problem instead of the generic pattern. For example, propagating transforms using the |= trick. That stuff was great for me.