I fear we have misunderstood game development

Main Ideas, Concepts, and Lessons

• Game development is far more iterative than most players realize

  • Even if a writer has produced lines/scripts, the final dialogue must be tested and adjusted once characters, level geometry, spacing, pacing, and gameplay context are physically present in the engine.
  • Levels often change after dialogue is written, which forces further revisions to keep timing and transitions coherent.

• “Playing the game” in development often means playing the specific chunks you wrote or worked on

  • Developers usually replay the relevant sections repeatedly to ensure their work triggers correctly in the final 3D context (timing, spacing, breath/space for beats).
  • It’s often faster to review updated scripts than to boot devkits, deal with security/protocols, download builds, and play other people’s levels.

• Cross-disciplinary collaboration can transform small writing into major in-game elements

  • A writer might provide something as small as a sentence (“TBD puzzle”), or a basic animation placeholder, but other departments (design, art, animation, programming) can expand it into elaborate sequences.
  • This collaborative expansion is portrayed as one of the most rewarding parts of the job.

• Common assumptions about game dev—salary, time spent playing games, meetings, crunch—are mostly incorrect or oversimplified

  • Assumption: devs spend all day playing games → generally false; in production, devs often play less than ever besides their current project, though they may discuss games constantly.
  • Assumption: devs are making tons of money → most developers make little to moderate pay; AAA has a wider range, salaries vary heavily by location/cost of living, and many workers are not “rich.”
  • Assumption: crunch is mainly because devs are lazy → presented as mostly wrong; crunch is commonly caused by overpromising, milestones, technical/health setbacks, and leadership/corporate funding pressure.

• Crunch is driven by milestone deadlines and funding risk, not just worker laziness

  • Producers manage progress toward milestone deliverables (e.g., completing a level).
  • When tasks take longer due to human factors (illness, death in family, accidents, hiring delays) or technical factors (unexpected bugs, underestimated complexity), teams fall behind.
  • Since funders typically care primarily about hitting due dates, overtime becomes the pressure response (“enter crunch”).
  • The speaker argues that if crunch happens, the blame often belongs more to leadership/game direction choices (what gets cut, timeline accuracy) than to the team’s effort.

• Engine decisions affect visual output more than players may think

  • The speaker emphasizes that an engine (shaders, rendering pipeline) heavily influences graphics results; the same face scan can look radically different across engines.
  • Artists design characters, but the “engine makers” are responsible for the underlying tech that determines how data is rendered.

• Working on games changes how developers experience them as players

  • Developers may not want to play the shipped version because they’ve seen/iterated it already, or because the process has removed the “new” discovery feeling.
  • Even when they don’t play a release version, they may still appreciate differences as a “new perspective” rather than a ruined experience.

• Microtransactions and “players liking the game”

  • Developers are described as primarily caring about player experience and that the goal is for players to like the game.
  • Microtransactions are framed as publisher-mandated rather than something developers freely choose for profit motives.
  • Many developers still include content they personally dislike due to decisions, budget constraints, or hierarchy/publisher directives.

• The work is harder and more complex than it appears

  • Even simple-seeming features (like menus or font sizes) take much longer than players expect.
  • The speaker uses dramatic humor to emphasize how much breaks in development and how “nothing is simple.”

---

Methodology / Workflow Instructions (How Their Work Is Iterated)

Iterative process for narrative dialogue in a changing level

• Write dialogue lines in scripts/text documents
• Place/play-test the dialogue within the current level build
• Check in-engine context once the level is “physically present”
  • Verify spatial timing:
    • Are lines triggered too close together?
    • Too far apart?
  • Account for how a player will see/experience the beat in 3D space
• Respond to lead writer/game direction feedback
  • If a character beat isn’t landing as intended, adjust where dialogue fits naturally
  • Rework dialogue to hit pacing goals and address notes
• Re-play as the level continues evolving
  • Confirm whether later changes affected:
    • pacing
    • transitions
    • combat start timing
  • Update dialogue if earlier context makes lines suddenly feel “off”

Typical reason developers don’t fully “play the whole game” during production

• Focus primarily on the specific sections they directly authored/implemented
• Avoid costly/devkit workflow and build-download overhead unless shipping-near context is needed
• Prefer quicker review of updated scripts where possible

Crunch prevention framework (as implied by the speaker)

• Leadership/game director should constantly monitor
  • the rate of progress
  • what is being completed vs. what remains
• Cut or reduce scope proactively to prevent ballooning work as new ideas are added
• Adjust timelines realistically based on creative uncertainty and engine instability
• If deadlines are still slipping:
  • the speaker argues responsibility should more often be on leadership decisions (scope/timing), not on forcing teams via overtime

---

Speakers or Sources Featured (as named in subtitles)

• Quince (video sponsor; clothing/home goods brand)
• Neil Druckmann (mentioned as an example of a very high-profile game industry figure)
• Andrew Wilson (CEO of EA; referenced in salary comparison context)
• Steven Totilo (referenced via a “Game File” chart he makes)
• Josh (video editor/artist on Layers Deep; also answers about engines vs. character design)
• Billy Basso (named as creator of Animal Well; referenced as an example of an indie making everything)
• J. (implied “Game Developers Choice Awards” speech; specific speaker not additionally named beyond the main narrator)
• The narrator / main speaker (unnamed in subtitles; described as a narrative designer/writer who worked on God of War Ragnarök and other projects, and is developing Layers Deep)

---

Additional Game Titles and Engine References Mentioned

• God of War Ragnarök
• Laufey (as referenced by the narrator; likely a project name)
• Layers Deep (indie game under development)
• Dispatch (game with voiced character “Malevolent”)
• Animal Well
• Hollow Knight
• Blasphemous
• Decima engine (engine referenced)
• Fallout and League of Legends (engine/output comparisons mentioned)