Skip to content
Tech News
← Back to articles

There are a few things that I look back on as my mistakes in the early days

read original more articles
Why This Matters

This article highlights the lessons learned from the early development of Quake, emphasizing the importance of realistic project scope, team management, and strategic planning in tech innovation. These insights are valuable for both industry veterans and emerging developers aiming to build sustainable and successful gaming and tech companies.

Key Takeaways

There are a few things that I look back on as my mistakes in the early days. Quake was overly ambitious technically. We could have done all the great multiplayer and modding work inside a Doom++ engine, allowing the designers to work with a more stable base instead of rug-pulling everything out from underneath them a couple times. The follow up game could have then brought in full 6DOF environments and characters. I pushed everyone too hard. I didn’t appreciate how maturing companies need more slack, and that running people at startup intensity constantly will wear them out. Quake was also where I really had to accept my personal limits. I was working pretty much as hard as humanly possible, and I was still slipping past my goal points. On all of the founders’ shoulders, our original corporate stock arrangement and buy/sell agreement was a mistake, and resulted in bad incentives. We wanted to ensure that all ownership rested in the hands of people working hard on current projects, but the Silicon Valley standard approach of vesting stock would have worked out better. One real problem that I don’t accept the blame for is that we were insisting that level designers be not just game designers, but also have strong visual design esthetics. They needed to make things that not only played well, but looked awesome, and it got more challenging as the technology provided a richer palette. Romero covered that well, which set our company expectations early on. We should have figured out how to pair up artists and designers earlier, but there was infighting among the designers, and the ones that could manage the visuals were happy to disparage the ones that couldn’t. Sorry, Sandy.

Sandy Petersen 🪔 @SandyofCthulhu 16h How Quake ruined id Software. There has been a lot of praise of Quake of late, with its 30th anniversary, and it's deserved. Quake is an amazing feat of art, programming, and design. I worked on it, and everything came together almost perfectly from all of us. We ended up with Show more 00:00