TThe Tim Ferriss Show
← All episodes
John Romero12 July 2023

#681: Doom Legend John Romero — The Path to Prolific Innovation and Making 130+ Games, How to Find the Soul of the Work, Audacious Ambition, and Building in Monk Mode

4Frameworks
10Insights

Frameworks in this episode

Insights & moments

The myth-busts, hot takes, explainers, and tools worth keeping.

Hot Take· 1

Hot Take1:06:30

DOOM Outlived the Team's Plan to Destroy It

id Software expected each new game to make the previous one obsolete and never anticipated DOOM remaining active for decades. Romero points to the continuing daily creation of mods, including MyHouse.WAD, as evidence that the game became an enduring creative platform.

  • The team's default assumption was that the next game would replace the last
  • DOOM remained actively extended for 30 years
  • Community modification created a lifespan its makers did not predict

But up until that point, every game that we made, we would put it out and then our plan is to just wipe that game…

John Romero · 1:06:30

Stuff is being made for the game on a daily basis all the time.

John Romero · 1:07:00
#doom#modding#community

Explainer· 1

Explainer49:00

How Hyperthymesia Shapes Romero's Work and Memory

Romero defines hyperthymesia as unusually strong autobiographical recall and says he remembers significant events and connected details across programming, music, movies, and games. It helps him retrieve earlier solutions and avoid failed designs, but can also make insignificant details feel more important because of their connections.

  • Romero retains significant autobiographical and technical details
  • Recall helps him retrieve prior solutions without rediscovering them
  • Connected memories can distort the perceived importance of small details

Yeah, hyperthymesia is a memory disorder where the person with hyperthymesia has a superior autobiographical recall.

John Romero · 49:00

I think a lot of things are similar in importance even if they aren't.

John Romero · 54:00
#memory#hyperthymesia#cognition

Story· 7

Story01:30

The Childhood Hardships Behind Romero's Resilience

Romero describes growing up poor near the Yaqui Reservation in Tucson, surrounded by heavy drinking before his father left. Ferriss adds documented context about abuse, scarcity, and an episode in which Romero and his younger brother were abandoned in the desert.

  • Romero's paternal family has Aztec and Yaqui heritage
  • His early home environment was poor and shaped by alcoholism
  • His mother later remarried and moved the family to Northern California

We lived in a pretty poor place.

John Romero · 02:00

My dad went to the grocery store and never came back, and so my mom got a divorce and then met a guy that was…

John Romero · 02:30
#childhood#resilience#family
Story06:30

How a Teacher Found Romero a Classified-Squadron Coding Job

After Romero demonstrated that he already knew BASIC and assembly language, his new teacher took him to the Aggressor Squadron on his second day at school. He recognized the Cromemco computer's operating system and programming language and was hired immediately.

  • Romero entered the class already beyond its BASIC curriculum
  • His teacher connected demonstrated ability to a real opportunity
  • Recognizing CP/M and BASIC let him start without additional training

And the second day when I came to school, she told everyone in the class what to work on and then she told me to…

John Romero · 07:30

He is like, "You've got yourself a job."

John Romero · 09:00
#career#programming#opportunity
Story10:00

Learning to Code Three Years Before Owning a Computer

At 11, Romero followed a friend to a college computer lab because its games did not require quarters. He asked a student how games were programmed, used the lab's BASIC book to teach himself, and later practiced by typing code into display machines in computer stores.

  • Free text games first drew Romero into the college lab
  • Curiosity about how the games were made led him to programming
  • He practiced opportunistically in stores before owning a computer

I just found a way for us to play games that doesn't cost any money.

John Romero · 10:00

11-year-old goes to computer lab at the college and teaches himself how to code.

John Romero · 12:30
#learning#programming#curiosity
Story1:14:00

How Quake's Moving Technology Target Burned Out the Team

During Quake's development, level designers repeatedly created work for an engine that kept becoming faster and more capable, leaving earlier levels too primitive to use. By the time the engine was ready, the team lacked the energy for another undefined design challenge and spent seven months in crunch mode to ship a shooter.

  • Changing engine capability repeatedly invalidated level work
  • The medieval game's design had no bounded finish line
  • The team crunched seven days a week for seven months

The engine could do more than what they had created.

John Romero · 1:14:00

We don't have a scope that has an end on it now.

John Romero · 1:16:00
#quake#burnout#scope#game development
Story1:17:00

Why Romero Left id Software After Quake

Romero had been planning to leave because he believed id was becoming a technology company rather than continuing to push game design. After Quake shipped, he separated from the company and began building relationships with publishers to start Ion Storm with Tom Hall.

  • Romero wanted design ambition to advance alongside technology
  • He planned his departure months before Quake shipped
  • He viewed leaving as both painful and creatively exciting

I was already planning for half a year to leave because if we're not going to commit ourselves to furthering design, it's just going to…

John Romero · 1:17:30

It was like that was a lot of really great work there but I'm also excited about what I can possibly do with without limitations…

John Romero · 1:19:00
#career#id software#ion storm
Story1:20:00

Why Romero Wrote DOOM Guy

A speaking organizer asked Romero to explain the life that made him the person who could create DOOM rather than retell DOOM's development. Audience reaction convinced him to combine his previously private early-life story with an authoritative chronology of the games and software he helped make.

  • A request for an unfamiliar talk surfaced Romero's childhood story
  • The audience told him the material belonged in a book
  • The memoir combines personal history with a software chronology

Can you tell us about your early life and what made you the person that would make DOOM.

John Romero · 1:20:30

So it was kind of a twofold reason for writing the book was to get the whole story out there from when I was born…

John Romero · 1:21:30
#memoir#doom guy#storytelling
Story1:22:30

The Movie Line That Gave DOOM Its Name

John Carmack heard Tom Cruise answer “It's doom” when asked what was inside his cue case in The Color of Money. He proposed DOOM as the game's title, and Romero immediately agreed.

  • The title came from The Color of Money
  • Carmack proposed the name after hearing the cue-case exchange
  • Romero says the team had not heard of another game called DOOM

And the guy's like, "What's in there?" And Tom Cruise looks down at it and looks up at the guy and goes, "It's doom."

John Romero · 1:23:00

So he said, "How about DOOM?" And I was like, "That is awesome. Yeah."

John Romero · 1:23:00
#doom#naming#film

Takeaway· 1

Takeaway14:30

Why Immediate Feedback Accelerated Romero's Learning

Early computers booted directly into a programming environment, letting Romero type, run, fail, correct, and learn almost immediately. That tight feedback loop sustained his attention and turned small solved problems into confidence that larger ideas could be built.

  • Early machines were ready to code as soon as they started
  • Every run produced an immediate success or correction signal
  • Accumulated small solutions created confidence for larger designs

So the iteration speed of learning was as fast as it gets.

John Romero · 15:00

When you start breaking down all of these little problems and you know how to solve one of these little problems, you start to have…

John Romero · 16:00
#learning#feedback loops#programming