Listening While Building

I finished the Masters of Doom audiobook a few nights ago and I miss it. That is the only honest way to start this. I had it running while I worked on my own projects, the way I do, and then it ended and the room felt a little quieter than it should. Marvelous is the word I keep landing on. It stuck with me the same way Shoe Dog stuck with me, where the story keeps replaying after the final chapter and you find yourself wanting more of a thing that is already over.

Wil Wheaton narrates this one, and that choice is perfect. He reads it the way the book deserves to be read: fast, charged, a little giddy about the technology, never flat. When Carmack cracks side-scrolling on a PC nobody thought could do it, Wheaton sounds like he is sitting next to you trying not to spill his Coke. The energy in the narration matches the energy in the work itself. I listen to a lot of these books while I build, and the ones that win are the ones where the voice keeps pace with my own pulse. This one did.

Masters of Doom by David Kushner, the story of id Software

David Kushner wrote this in 2003, and the structure is simple: two guys named John build an empire out of a Texas apartment, transform an entire medium, and then tear each other apart at the top of the mountain. Commander Keen. Wolfenstein 3D. DOOM. Quake. The titles alone are a timeline of the moment PC gaming stopped being a hobby and became a force. I build games and films and music and software with AI agents now, so this story does not read like history to me. It reads like a mirror held at an angle.

Two Johns, Two Engines

The whole book lives in the contrast between the two founders, and it is the most useful thing in it.

John Carmack is the monk. He optimizes. He reads the hardware until he understands it better than the people who shipped it, and then he makes it do something it was never supposed to do. He is the one who looked at a PC in the late eighties and decided smooth side-scrolling was possible when every adult in the room said it was not. He works in long, silent, obsessive blocks. He gives things away. He famously does not care about the money the way you would expect a person sitting on that much of it to care. He cares about the next hard problem, and the one after that. Reading him, I recognized the engineer who cannot leave a working system alone because it could be faster, leaner, more elegant.

John Romero is the showman. The designer. The one who turns Carmack's engine into a world you want to live inside, who understands that a player does not feel the rendering math, the player feels the fear in the hallway and the joy of the rocket launcher. Romero is loud, hungry, magnetic, the guy who sells the dream out loud while Carmack builds the thing that makes the dream real. The famous line about being so good it makes the player a god is pure Romero energy. He gives the work its face.

You need both. That is the lesson buried under all the pizza boxes. The technical genius alone ships a tech demo. The showman alone ships a pitch deck. Together, in the same cramped room, fueled by Coke and deadlines and a shared certainty that they were doing something nobody else could, they shipped DOOM. I sit on both sides of that table depending on the day. Some days I am Carmack, head down in the architecture, trying to make the agents do something the tooling claims is impossible. Some days I am Romero, building the experience, caring about how it feels to a person who will never see the wiring. The split inside id is the split inside any one builder who is paying attention.

Shareware, the Garage, and Shipping Relentlessly

The origin is the part that hit me hardest, because it is the part I am living.

They started on borrowed time and borrowed machines. Apple II tinkering as kids, then a software shop, then a lake house, then that apartment where the legend gets made. No funding in the way we mean it now. Their distribution model was shareware: give the first chunk away for free, let it spread on its own through bulletin boards and floppies passed hand to hand, and charge for the rest. They let the work travel before they asked anyone for a dollar. The audience built the empire by copying the game to their friends. There is something in that I keep turning over, because it is exactly the posture I take with my own creative technology: ship the thing, let it move, let motion do the selling.

And they shipped constantly. That is the rhythm of the whole middle of the book. Build, ship, learn, build the next one faster. Commander Keen funds the engine that funds Wolfenstein that funds DOOM. Each release is the rocket fuel for the next. No long polishing phase where the thing sits in a drawer getting perfect. Good enough, out the door, on to the harder problem. I wrote almost the same idea about Phil Knight and the thirty-five dollar swoosh: perfectionism kills momentum, iteration beats it. id lived that at a pace that still feels reckless and is probably the only reason DOOM exists.

The two-founders dynamic and shareware era that built DOOM

Then there is deathmatch. The book treats the moment multiplayer DOOM clicks as a kind of detonation, and it was. They did not just make a game, they made a thing people did to each other, in the same room and across the wire, and the culture that grew out of that is still here. That is the part that gives me a little vertigo: they could not have predicted what deathmatch would become, the same way nobody building anything truly new gets to see the far edge of it from the apartment.

Book Details at a Glance

Feature	Details
Title	Masters of Doom: How Two Guys Created an Empire and Transformed Pop Culture
Author	David Kushner
Publication Year	2003
Genre	Nonfiction, Technology, Business, Gaming History
Length	~330 pages (audiobook: ~12.5 hours)
Subjects	John Carmack, John Romero, id Software, Commander Keen, Wolfenstein 3D, DOOM, Quake
Main Themes	Founder dynamics, technical breakthrough, shareware distribution, crunch culture, shipping relentlessly, the eventual split
Key Insight	The engine and the showman are two halves of one machine; you build empires when both run hot in the same room
Audiobook Quality	Excellent. Narrator: Wil Wheaton, fast and charged, matches the kinetic energy of the story
Who Should Read?	Game developers, builders of creative technology, two-founder teams, anyone shipping hard things from a small room

Why This One Resonated With Me

I make creative technology for a living now, and I make a lot of it with AI agents working alongside me. I wrote recently about why I build creative technology and about how AI is changing software engineering, and reading Masters of Doom felt like watching the ancestors of that work move at the highest speed their era allowed. Carmack squeezing impossible performance out of a 386 is the same instinct as squeezing a whole production pipeline out of a swarm of agents. Different decade, same hunger, same refusal to accept the limit you were handed.

One of the things I build is Pixel Vault, a playable museum of game design. So a book about the people who invented modern game feel, who decided what a first-person shooter even is, lands in the exact center of the thing I care about. These two Johns are in the foundation of the medium I build inside. Walking through the history of DOOM while building a place that celebrates that history is a strange loop I enjoyed every minute of.

And the crunch culture, the pizza and Coke and all-night sessions and the sheer intensity of it, I recognized that too, though I try to channel mine into flow rather than burnout now. There is a version of that energy that is destructive and a version that is sacred, and the book holds both without flinching.

And maybe I caught a little of my own fearlessness from this book. I am shipping constantly right now, music through ChipForge AI and films through Napkin Films AI, and that pace only works if you stop flinching. Carmack and Romero did not sit on Wolfenstein polishing it into a museum piece. They shipped it and started the next one. That is the permission I keep needing to hear out loud. Make it, push it out, learn in the open, improve on the next pass. Do not look back to sand down what already left the building. You have to be a little fearless and stop giving a damn whether anyone thinks it is ready, because the only version that counts is the one that is out in the world. Keep moving forward. The next one is always better than the one you were tempted to polish into the ground.

The Split

I will not spoil the ending for anyone who has not lived it, but the empire does not stay whole. Two engines running that hot, that close, eventually grind against each other. The same difference that made id unstoppable, the monk and the showman, is the difference that pulls them apart at the summit. Kushner does not moralize about it. He lets it hurt a little, which is the right call. Building something extraordinary costs something, and the cost is rarely the part anyone warns you about. That honesty is what lifts this from a gaming-trivia book into a real founder story, the same honesty that made Shoe Dog matter.

Final Word

This is one of the best builder stories I have taken in, and the audiobook is the way to take it in. Wheaton's narration carries it like a current. I finished it and I missed it immediately, and a few weeks later I still do. If you build anything from a small room with too little money and too much certainty, if you have ever been the engine or the showman or both in one week, read it. (Buy the audiobook on Amazon)

🎧 Get the Masters of Doom audiobook (Wil Wheaton narration) on Amazon

📖 Prefer to read it? Get the paperback on Amazon

Masters of Doom by David Kushner: How Two Johns Built id Software