Dwarf Fortress Developer Highlights Major Concern with AI: The Pressure to Adopt It

“Everyone I know, their bosses are slowly getting psychosis, right?” This statement resonates deeply within the gaming industry today. Tarn Adams, the mind behind the iconic Dwarf Fortress, shared this insight during a conversation about the exhausting role of AI at Gamescom. “They’re trying to have a CEO press a button that makes a game, and then everyone else somehow buys it without a job.”

While many gamers express strong opposition to the use of generative AI for creating art, assets, voices, or sound in games, the reality is that its most prevalent application lies in the coding itself. Public outcries and Steam declarations often overlook how much of the coding landscape is currently dominated by tools like Claude and Copilot, largely due to pressures from management. Why invest weeks in crafting solid, functional code when you can simply prompt an AI to whip something up and test it? Aside from, you know, all the obvious reasons.

Adams highlights this issue when he notes that bosses are often fixated on whether AI was used in code commits. “They’re just like, ‘yeah, but did you use AI on your commits?’ And then they’re like, ‘oh well, I’m not happy with this guy.’ You know, ‘We’ll probably have machines do the job.’” He reflects on this with a sense of frustration, likening it to a Dead Kennedys song. “It’s just the same old shit. I mean, they laid off my dad from the sewage treatment plant because they didn’t understand what his job was, and he was the computer guy there, and they don’t have a company anymore, so it’s…the same old shit.”

This scenario is unfolding across all coding jobs, not just in gaming, where executives are lured by the empty promises of AI—promises of time-saving efficiencies through this so-called magic tool—and then impose unrealistic expectations on their teams. The reality is that debugging AI-generated code can often take much longer than writing it from scratch, not to mention the long-term risks of software created without full oversight. Yet, there’s an expectation that Claude can deliver faster, all while using a fraction of the resources it would have required last year.

“I don’t see it going anywhere sustainable,” Adams states, “and I feel like there will simply be a pop and a reckoning and then [it’s on repeat] unless people do something else.”