The post is a Carmack reply to Sandy Petersen’s anniversary thread arguing that Quake was a masterpiece that also “ruined” id Software by gutting the team that made Doom-era id special. Carmack agrees with more of that diagnosis than many expected. He says he pushed everyone too hard, failed to leave enough slack as the company matured, and handled people issues badly. He also points to a specific structural mistake in how id treated level designers, expecting them to be both strong gameplay designers and strong visual artists instead of pairing those roles earlier. The “Sorry, Sandy” line landed as a genuine apology for failing to resolve that setup and the conflict around it before Petersen left, not as a jab.
People largely accepted the core story that Quake was both a historic technical leap and a breaking point for the company. The strongest throughline was that id’s early greatness came from a rare balance of technical and creative talents, and Quake strained that balance until it snapped. Carmack could still ship world-changing engine work. What id struggled to replace was the mix of level design, art direction, and product sensibility that turned engine breakthroughs into era-defining games. That is why many comments treat Quake as the last moment id was plainly ahead of the field, then describe Quake III as excellent but narrower, Doom 3 as technically bold but less influential, and Half-Life 2 or Unreal Tournament as signs the crown had moved on.
On the management side, readers seized on the startup lesson more than the game history. Once a company grows past a tiny, high-upside founding crew, the old pace stops making sense. Employees do not have founder equity, founder autonomy, or founder appetite for risk. Expecting 100 people to work like five co-founders is how you get burnout, politics, and mediocre output disguised as heroics. Several comments sharpened the point that mature companies often keep the mythology of all-out effort while quietly removing the upside that once made it rational.
There was still admiration for the result. A lot of people flatly said Quake was worth it, or at least understandable in context, because the leap to full 3D,
client-server networking,
QuakeC,
modding, and online multiplayer changed PC gaming for decades. But even that camp mostly did not defend the human cost. The practical consensus was not “don’t be ambitious.” It was that if you want repeated breakthroughs instead of one legendary product followed by a talent exodus, you need a company design that stops exceptional technical intensity from becoming the entire operating system.