John Carmack apologizes for Quake burnout after Sandy Petersen said it “ruined id Software”

The 30th anniversary of Quake just passed on June 22, 2026, and the celebration got an unexpected tone shift: instead of just nostalgia, you got an internal postmortem from the people who built the thing. Sandy Petersen, the co-designer who joined id Software in 1993, kicked it off with a blunt post on X: “Quake ruined id Software.”

Petersen didn’t mean the game wasn’t great. He called Quake “an amazing feat of art, programming, and design,” praised the development team’s execution, and argued it was “absolutely” worth the cost. But then he drew the hard line: the workload was so intense, he said, “it broke us spiritually,” and “Id Software was never the same after.” That pairing matters for decision-makers and operators today, because it is the rare admission that a landmark product can still break the company that made it.

Petersen also listed people who left id within “a couple years of finishing Quake,” naming John Romero, Shawn Green, Dave Taylor, Mike Abrash, American McGee, and Petersen himself. His point was not talent failure. “So plainly we didn’t depart because of some kind of talent issue,” he wrote. “We were all highly competent, just a little burnt out after the labor of Quake.” That frames Quake as a stress test the organization failed, not a talent gap the team couldn’t overcome.

Then John Carmack responded, and he went further than a rebuttal. Carmack said Quake was “overly ambitious technically,” and argued id “could have done all the great multiplayer and modding work inside a Doom++ engine,” keeping the foundation stable instead of “rug-pulling everything out from underneath them a couple times.” He also owned his contribution to the team’s strain: “I pushed everyone too hard.” Carmack said he didn’t appreciate “how maturing companies need more slack,” and that “running people at startup intensity constantly will wear them out.”

Carmack also brought in the incentive problem, and this is where the story stops being just gamer lore and starts looking like board-level governance. He wrote that on the founders’ shoulders, id’s original corporate stock arrangement and buy/sell agreement was “a mistake,” creating “bad incentives.” The company wanted “all ownership rested in the hands of people working hard on current projects,” but Carmack argued the Silicon Valley standard of vesting stock “would have worked out better.” He added nuance on the product side too: Carmack doesn’t think raising expectations for Quake-level designers was a mistake, crediting Romero with setting that bar early, and acknowledging they should have “pair[ed] up artists and designers earlier.”

He then addressed internal team dynamics directly. “There was infighting among the designers,” Carmack wrote, with “the ones that could manage the visuals” disparaging those “that couldn’t.” And in the middle of all the analysis, he made it personal, ending with: “Sorry, Sandy.” For Petersen’s part, the endgame came quickly. After Carmack’s apology, Petersen said he didn’t blame Carmack for how it all worked out and told Romero he “did an incredible job” on Quake. Romero then thanked Petersen for getting the conversation going, saying it “really was a hell of a game.” That back-and-forth is basically a case study in repairing trust after creative burnout, not just debating design choices.

John Romero’s input landed on a very similar theme, just with a different emphasis. He echoed the in-hindsight belief that they should have stuck with a Doom++ engine while ironing out the fully-3D Quake engine. He also pointed to a cultural accelerant: id’s founders had been “pushing ourselves past what was reasonable because that was how id had always worked.” Romero also gave specific credit to American McGee, calling him “really good” at building Quake levels, a pointed note given how McGee’s time at id ended. The source also references prior history: American McGee was reportedly fired by Carmack for sub-par performance on Quake, although Petersen later suggested McGee was “done dirty” by another employee. Romero added that “Having a media circus around us certainly didn’t help,” and closed with an almost philosophical summation: “id still goes on, and so does Wolf, Doom, and Quake. Maybe that was what we came together to do. That is more than enough for any game dev, any team, any lifetime really.”

So why should executives and board members care about a 90s engine debate? Because this conversation is the clearest form of operational truth: an organization can ship an iconic product while simultaneously mismanaging incentives, stability, and human limits. Petersen framed it as games being more important than game companies, with Quake as an “iconic titan.” Carmack framed it as leadership intensity and incentive design, plus technical overreach. Romero framed it as culture, expectations, and the cost of pushing “startup intensity” too long. If you run a company that wants “legendary” output, this is the caution baked into the praise: the dream can be real, and the harm can still be real too. The strategic stake for peers is not whether Quake was good. It was. The stake is whether your incentives, planning model, and internal tempo can produce greatness without shredding the people who have to live inside the process.