Attempting Deep Work

Storyline / Premise

The video is a talk (not a gameplay walkthrough) about how to sustain “deep work” in game development, especially across long multi-year projects. The speaker frames deep work as something that changes you, and argues that the biggest threats aren’t technical—they’re psychological, cultural, and environmental.

What “Deep Work” Means (Key Concepts)

• Deep work changes you: after doing it, you become a better (and different) practitioner—across design, programming, art, production, and management.
• You start without knowing the destination: deep work follows an internal guiding compass (personal curiosity/interest), not market demographics.
• It creates unique specialization: you end up with knowledge many others don’t have, because you follow an uncommon path.
• Most people don’t believe it’s happening day-to-day: culture makes developers downplay their work, so deep work can be misunderstood or unseen.
• It’s about the whole coherent work, not just inventing a new mechanic—visuals, code, design, and integration together.

Examples of “Deep Work” (Projects Referenced)

• Braid (development ~3.5 years) Deep learning in puzzle clarity, non-obfuscating communication, and how small changes can make puzzles weaker or stronger. The speaker later applies these lessons in subsequent work.

• The Witness (development ~5.5–6 years, ongoing in the talk) Expands from communicating ideas with short puzzles to longer streams of non-verbal communication through environment and puzzle design.

Gameplay / Development Highlights (Practical “How It Happens”)

The talk focuses on habits and strategies that make deep creative execution possible.

Generating Strong Ideas

• Ideas often arrive “from outside” (operationally) Like a modern version of the “muse” concept: whether from subconscious processing or elsewhere, you should act as if ideas are not fully under conscious control.

• Relaxed, receptive states unlock ideas, often during routine transitions:

  • shower, mornings
  • walking after lunch
• Physical hobby to trigger ideation
  • Recommendation: keep a regular physical hobby that’s enjoyable and relaxing (example: dancing).
  • Bring a way to capture ideas (notebook/notes).

Managing Existing Idea Backlogs

If you have many “almost-ready” ideas in your head, they can block new ideas.

Strategy:

• Clear the old list by reviewing uncertain ideas and deciding yes/no on them.
• After clearing, a new creativity window often opens.

What Sabotages Creativity (Major “Do-Not-Do” Factors)

• Scheduling: you can’t fully schedule an unknown destination; deep work requires going “when we get there.”
• “Child-proofing” (over-editing for acceptability)
  • watering down sharp creative edges so people won’t be confused/offended/unimpressed
  • reduces alignment with the original destination and undermines trust in your own ideas
• Chasing success
  • worrying about how others will judge the work (sales, reviews, “metacritic,” acclaim)
  • turns creativity into conformity
• Team politics / social pressure
  • doing things to be liked/validated within the team
• Distractions (especially interruptions)
  • even small interruptions break flow and prevent the relaxation needed for idea reception
  • example solution: leave an open-plan office to work elsewhere (e.g., a cafe or another room)

Long Projects: Keeping Deep Work Alive

Burnout (Primary Risk)

Burnout is described as a mismatch between:

• rational mind: “working is good; this is the plan”
• intuitive/animal mind: needs for comfort, connection, validation

It shows up as avoidance behaviors (e.g., drifting to web browsing/social media).

Prevention approach: manage the “human animal” needs:

• physical comfort (e.g., buying clothes that feel good)
• emotional/social connection (spending time with friends even if it isn’t always maximally enjoyable)

Meditation for Perspective

Meditation is used to reduce the emotional “loudness” of project fears/stories, helping the speaker re-check reality (“from first principles”) rather than engaging the doom narrative.

The “Cry Test” (Commitment Check)

To decide whether a project is worth years:

1. Imagine explaining it to a trusted intimate person in a safe setting.
2. If you don’t experience an involuntary emotional surge (not necessarily sadness), you probably don’t have enough core commitment.

Implication: long projects require “love” for the purpose—not just liking an idea.

Breaks and Vacations (What to Do When Exhausted)

Two acceptable recovery modes:

• real vacation (time away where you don’t think about the game)
• working breaks (make a smaller finished side game)

Critical warning:

• Don’t “force work” on tired weekends and then waste time scrolling—this creates a snowball of misery.

Rule of thumb shared:

• Only take a side-project break if it’s smaller than something you’ve already shipped.
• If you’ve shipped nothing, start small instead of abandoning the main project.

Preventing “Illusion of No Progress”

• Establish momentum early: strong productivity early means that later, when motivation dips, you can look back and see real progress.
• It also helps clear old ideas, reopening the creativity window.

Choosing a Project Baseline (Scope Control)

Deep work depends on your ability to sustain execution.

Pick an implementation baseline you can handle:

• Too hard a baseline can consume all energy, leaving no room for deep design exploration.

Example contrast:

• Braid was chosen partly because 2D platforming was “easy to program” relative to prior technical ambitions, leaving more room for design depth.
• The Witness supports larger ambition partly because of team scale; as a solo developer it would be impossible.

Key Tips (Condensed Checklist)

• Use a personal internal guiding compass (not demographics).
• Build deep work around the coherent entire work, not single mechanics.
• Trigger idea flow with relaxation + an enjoyable physical hobby; capture ideas immediately.
• Periodically clear the backlog of old tentative ideas (make yes/no decisions).
• Avoid creativity killers:
  • schedules for unknown destinations
  • “child-proofing” for acceptability
  • chasing success/judgment
  • team politics
  • distractions/interruption
• Manage burnout by meeting human needs (comfort, connection, validation).
• Use meditation (or similar perspective practices) to step back from fear stories.
• Do the “Cry Test” to ensure core commitment.
• Take recovery breaks:
  • full vacations
  • or working breaks via small completed side projects
• Create momentum early so later fatigue doesn’t create “no progress” despair.
• Choose scope/baseline you can execute so deep exploration remains possible.

Gamers / Sources Featured (Mentioned at the End)

• Paul Graham (Y Combinator) — referenced via “The Top Idea in Your Mind” (2010)
• David Lynch — referenced via Catching the Big Fish
• Muses (ancient Greek concept)
• Paul Cézanne — referenced via quotes about painting (carrot example)
• Jonathan Blow (the speaker; referenced as “Jonathan” in Q&A)
• Danielle Ben Murgui (mentioned as co-creator on a smaller side project)
• Examples named:
  • Adam / Jonathan / “Danielle Ben Murgui” / “Rod Humble”
• Rod Humble — referenced via The Marriage (example)

Games Referenced as Works by the Speaker

• Braid
• The Witness
• Earlier project (first professional game described): a multiplayer 3D action/strategy/war game using ~9600 modems (title not given in subtitles)
• Ernesto RPG (side project/prototype mentioned)
• Storyteller (ambitious game Danielle’s friend was working on; described as ongoing)