Chapter 40 — Quiz

Fifteen questions synthesizing the chapter's themes and drawing across the book's 40-chapter arc. The quiz is retrospective — some questions refer back to earlier chapters. Answer before checking the key at the bottom.

Questions

1. According to the chapter's framing, which sentence is "the most important sentence in the book"?

a) "Design is systems, not ideas." b) "Your first game will be bad — ship it anyway." c) "You finished a game. Very few people ever do." d) "Play is how humans learn."

2. The chapter argues that the six-section post-mortem structure originated in which publication?

a) Edge magazine in the 2000s. b) Game Developer Magazine (and later Gamasutra) in the late 1990s. c) GDC Vault submissions in the 2010s. d) Rock Paper Shotgun devlogs.

3. The chapter describes two failure modes of post-mortem writing. Which are they?

a) Listing too many items and listing too few. b) Defensive minimization and self-flagellating catastrophe. c) Excessive length and excessive brevity. d) Technical detail and marketing fluff.

4. The chapter recommends writing the post-mortem within what window after shipping?

a) Within 48 hours. b) Within a month, with a draft of "what went wrong" in the first week. c) Within a year, once perspective has stabilized. d) Whenever inspiration strikes.

5. Which of the following is NOT on the chapter's list of what belongs in a designer's portfolio?

a) The shipped game itself (trailer, screenshots, playable build). b) Design documents and selected exercises from the book. c) Your published post-mortem. d) A long list of abandoned prototypes to show range.

6. The chapter's cover-letter prescription says the first paragraph should open with:

a) A confession of lifelong passion for games. b) A specific observation about a craft decision in the studio's most recent game. c) A summary of your shipped game. d) A quote from the studio's founder.

7. Which of the following best captures the chapter's rule about networking?

a) Attend every industry event you can afford. b) Cold-message senior designers with clear, concise asks. c) Give before you take; participate consistently in a few chosen venues over years. d) Maintain separate networks for each platform to maximize reach.

8. The chapter describes the progression from "the first game" to "the second game" as:

a) A scale-up: the second game should be 2-3x the scope of the first. b) A consolidation: vocabulary becomes language; same-scope project executed with the first project's lessons. c) A pivot: the second game must be in a different genre than the first. d) A reset: discard everything you learned and start fresh.

9. Theme 1 from the book's seven themes is:

a) Your first game will be bad — ship it anyway. b) Design is systems, not ideas. c) Fun is not an accident. d) Games teach through play.

10. The chapter names several designers as examples of "shipped a bad first game, then made a great one." Which of the following is cited?

a) Hideo Kojima (pre-Metal Gear). b) Toby Fox (pre-Undertale EarthBound ROM hacks including Radiation's Halloween Hack). c) Shigeru Miyamoto (pre-Donkey Kong). d) Gabe Newell (pre-Half-Life).

11. Which of the following is given as a canonical example of a post-mortem the chapter urges you to study?

a) Peter Molyneux's Fable II post-mortem. b) Matt Thorson and Noel Berry's Celeste post-mortem. c) Hideo Kojima's Death Stranding post-mortem. d) Todd Howard's Skyrim post-mortem.

12. The chapter argues that if you cannot find a specific craft observation to open your cover letter with, it means:

a) You need to play more games in the genre. b) The job is probably not a fit for you; find a studio whose work you can actually speak to. c) You should fall back on a generic passion-for-games opener. d) The studio is probably not a good match for entry-level designers.

13. The chapter's "When to Walk Away" section makes which claim about design skills?

a) Design skills only apply inside the games industry. b) Design skills transfer to UX, product design, software engineering, teaching, and writing — the craft travels with you. c) Leaving the industry means the skills decay within two years. d) Walking away is only valid after three shipped projects.

14. Theme 7 — "Your first game will be bad — ship it anyway" — is defended in the chapter on what grounds?

a) The first game will probably actually be good; the theme is an intentional provocation. b) A bad shipped game teaches more than a beautiful unshipped game; shipping forces completion, completion forces decisions, decisions build skill. c) Players expect first games to be bad and grade them on a curve. d) The first game's badness is proof of authenticity that players will reward commercially.

15. The chapter closes by claiming that making games is:

a) A frivolous pursuit best treated as a hobby. b) Only valuable when the games are commercially successful. c) Contributing a small object of delight to the world — not frivolous work. d) A calling that requires complete commitment to the exclusion of other careers.

Answer Key

1. c. The chapter opens with "You finished a game. Very few people ever do," and immediately tells the reader this is the most important sentence in the book. The point is that completion is the rarer achievement than quality, and completion is the prerequisite for every subsequent craft lesson.

2. b. Game Developer Magazine (and later Gamasutra, the sister website, now GameDeveloper.com) popularized the six-section post-mortem format in the late 1990s. For twenty years, the Gamasutra post-mortem was the de facto yearly inheritance for indie designers learning the craft.

3. b. The two failure modes named in the chapter are defensive minimization ("we had some small challenges but mostly things went fine") and self-flagellating catastrophe ("I am terrible, the game is terrible"). Both fail the purpose of the post-mortem, which is to surface specific, useful lessons for other designers. The stance the chapter recommends is clinical — a doctor's stance, not a patient's.

4. b. The chapter specifies writing within a month, with a draft of the "what went wrong" section within the first week post-crunch, when those memories are sharpest and the lessons have not yet softened into generalities. After six months, the specificity is mostly gone.

5. d. A long list of abandoned prototypes is the opposite of what the chapter recommends. Curate ruthlessly — the shipped game is the headline piece, everything else supports or gets cut. A small, deep portfolio beats a large, shallow one.

6. b. The chapter prescribes opening with a specific observation about a craft decision in the studio's most recent game. This demonstrates design thinking in the letter itself and differentiates the application from the generic "I have always loved games" opener that every hiring manager has already read five hundred times.

7. c. The chapter's networking rule is "give before you take" — contribute to a few chosen communities consistently over years. Depth beats breadth. The anti-pattern is cold-messaging senior designers without prior interaction, which "almost never works and poisons future interactions."

8. b. The chapter argues the second game is where vocabulary becomes language — same scope as the first, executed with the first project's lessons. Scope up on the third or fourth game, not the second. The scope-creep-on-second-game pattern is named as the most common way first-time shippers never ship again.

9. b. Theme 1 is Design is systems, not ideas. Ideas are free; the craft is in implementation, testing, refinement. The other options are also book themes (Themes 7, 6, and 5 respectively), but Theme 1 is specifically the systems-not-ideas claim.

10. b. Toby Fox's pre-Undertale work — including the EarthBound ROM hack Radiation's Halloween Hack from 2008 — is cited as a classic example. The chapter names this alongside Eric Barone's early Stardew rewrites, Markus Persson's abandoned pre-Minecraft projects, and Derek Yu's early freeware platformers.

11. b. Matt Thorson and Noel Berry's Celeste post-mortem is singled out as "a masterpiece of specificity." Eric Barone's Stardew Valley post-mortem and Lucas Pope's Papers, Please post-mortem are also cited. Toby Fox is noted as having distributed his reflection across interviews rather than writing a single traditional post-mortem.

12. b. If you cannot find a specific craft observation to open the cover letter with, the chapter's diagnosis is that the fit probably is not there. Find a different studio whose work you actually admire and can speak to. The cover letter is a symptom; the underlying issue is studio-candidate fit.

13. b. The skills travel. Design thinking is one of the most transferable skill sets in knowledge work — applicable to UX, product design, software engineering, teaching, and writing. The chapter's stance is that walking away from the industry does not mean walking away from the craft.

14. b. The defense is that a bad shipped game teaches more than a beautiful unshipped game. The mechanism: shipping forces completion, completion forces decisions, and the thousand decisions of shipping are a thousand units of learning. The unshipped game stays in your head, perfect and untested.

15. c. The chapter closes with the claim that making a game is contributing a small object of delight to the world, and that this is not frivolous work. Play matters — as learning, as connection, as expression — and the designer who ships a game has added to the collective human project of building systems people can play with.

Scoring

• 14-15 correct: You have internalized the capstone chapter and the book's synthesis of its themes. You are ready to ship, reflect, and move to the next project.
• 11-13 correct: Strong grasp. Re-read the sections on the post-mortem structure and the 7-themes revisit — they are the two sections most likely to reward a second pass.
• 7-10 correct: Partial grasp. Return to the chapter, this time making notes. The post-mortem section is the action item most worth focusing on — it produces the document that will repay the rest of your career.
• 6 or fewer: Re-read the chapter. But also — and this is more important — ship your game regardless. The quiz score does not matter. The shipped game does.