In this chapter, we took the time to review the current draft of the design document of the book's game project. This draft of the GDD might not be complete or perfect, but often, game projects start with incomplete design documentation and ideas. So it's still good that we took the time to review it. We will not implement every system, mechanic, and ingredient described in this book because our primary goal is to learn design patterns by building a game, not necessarily a complete one.
Even though game design is not the main subject of this book, learning to think like a designer is a skill that can only help anyone become a better game programmer. Reading design documentation helps us understand the game's vision, structure, mechanics, and scope. And these are things to keep in mind when making software architecture decisions.
The next chapter includes a short primer on basic Unity programming fundamentals. If you are already an experienced programmer, you can...
