I am sure there are interesting insights and lessons and details if you're into game development, but the book is about a game engine - and underlying hardware of the same era - that is 25 years old.. So, caveat emptor?
I read a similar book a few years back. I think it was called "Game programming bible" or something. While the techniques were interesting, more interesting was the way developers solved critical problems (like large scale collision detection).
However, in this day and age, almost all low level problems have been extracted away by game engines such as Unity / Unreal, etc. The relevancy of the book as a manual to learn seem limited, looks more of an interesting read than a helpful resource.
