Summary
Highlights
Tim recounts using whiteboards to track game features and bugs for Fallout, enabling quick problem-solving without complaints. Ten years later at Carbine, attempting the same method was met with strong resistance from employees who threatened to quit, illustrating a shift in workplace dynamics and an aversion to public accountability.
During the development of The Outer Worlds, Tim requested a simple combat aggression AI feature that he estimated would take less than an hour to implement. This request was initially estimated at four weeks by a programmer and the lead programmer, who resisted Tim's attempts to simplify it. Eventually, they settled on a two-week estimate, highlighting a trend of inflated time estimates and reluctance to embrace rapid, simple solutions.
Tim describes his and Leonard's passionate, loud debates during game development, often misunderstood by colleagues as arguments. He clarifies these intense discussions are how they effectively flesh out ideas. This anecdote illustrates how an open, passionate approach to development can be misconstrued in a cautious environment.
Tim identifies a growing trend of 'development caution' in the industry, leading to padded time estimates, excessive meetings, and a reluctance to take risks. While acknowledging that increased game budgets contribute to this caution, he worries it stifles innovation, leading to less charming and more mundane games. He argues that this caution is also evident in game journalism, where fear of losing access leads to softer, less critical reviews.
Tim discusses how the shift in game development from artistic expression to corporate-driven, money-seeking ventures has been exacerbated by caution. He notes that while indie games often excel in ideas due to their willingness to take risks, AAA titles tend to borrow features from them. This caution also affects game journalism, leading to safer reviews focused on clicks rather than genuine passion or critique.
Tim encourages developers to embrace rapid iteration, make direct decisions, and be willing to discard ideas that don't work. He shares how he adapted to development caution by creating his own public Confluence page for bug tracking, an alternative to the rejected whiteboard. He also notes how his expectation for faster development on the combat AI led him to be perceived as an 'ogre,' and how he and Leonard continued their passionate discussions despite others' discomfort, believing such active engagement is crucial for game development.