4 of 5 people found the following review helpful
Practical advice for the underperforming developer,
This review is from: Game Architecture and Design (NRG - Programming) (Paperback)
This book, though well worth reading, is definitely a mixed bag. Split broadly between game design and game production, both are covered quite extensively but with a lot of repetition.
It starts well when describing different aspects of game design, listing some key concerns and doing well at steering clear of the "first, pick a genre" trap. But when it comes to the details of low level design, it seems to settle on the "everything is rock-paper-scissors" approach. There are some interesting variations on this theme, but some alternative perspectives would have been welcome, especially those that might hold true beyond the RTS/FPS ground that the mathematical approaches model well.
When it comes to the production process, the book seems to be squarely aimed at the underperforming team rather than the average or good one, as much of the advice seems to assume dysfunctional relationships, poor management, and a team of selfish developers. In fact, several of the tips given are tempered by telling us that top sellers like Doom and Starcraft "probably didn't use" some of these tricks, because they were too good to need to. In other words, Rollings and Morris go down the route that many others use when advocating their methodology, extolling it as a system to get the most out of a mediocre developer, rather than a way to create a great product.
Later parts of the book tend to repeat a few general themes, such as iterative development, focusing on creating working components and code-reuse, the merits of design patterns, etc. Most of these things are well-known to the educated developer, and repeated insistences that they are worth using (with graphs of arbitrary data to help convince us) are not going to change any minds.
Some parts seem opinionated and dogmatic, and sometimes even contradictory. Why suggest that imposing an arbitrary dress code will somehow make people work harder in the absence of cited evidence? Why waste time caricaturing five different types of 'problem developer' (which in this case is assumed to be synonymous with 'problem coder' - artists and designers are obviously perfect!) instead of just tackling the individual issues? Why use the phrase "start with a well-designed product, and then plan the marketing" in a sample design document, but in the very previous chapter make it very clear that you think the Marketing department should be treated by the developers as the end client for the product?
This last point is perhaps the most important one; this book is not about how to make good games as such, but about how to make enough of the resources at your disposal to make a game that is good enough and marketable enough to keep you in business. There is enough common sense here to turn any randomly-assembled rabble of developers into a group that can probably ship something, given management with enough determination. But if you're already at that standard, or are able to work outside the constraints of a typical professional team of developers, most of the knowledge here will be of limited use.