Abstract
Problem: What makes game development truly meaningful — the process, the end product, or something else entirely?
Approach: Tim Cain reflects on a question from fellow Interplay veteran Bruce Schlickberger, drawing on 42+ years of experience, personal memories, and the loss of colleagues to articulate what game development really meant to him.
Findings: It's not the process or the product — it's the people. The day-to-day experience of working alongside talented, passionate teammates is what made projects like Fallout special. Cain shares a never-before-told memory of standing in his office doorway during Fallout's development, simply listening to his team work, and realizing years later that this quiet moment captured everything he loved about making games.
Key insight: Game development is about the people you make games with, not the games themselves — and you should tell those people what they mean to you before it's too late.
The Question
Tim responds to a question from Bruce Schlickberger, a fellow Interplay colleague: "Is it about the process or the end result?" Tim's initial answer was "the process" — citing early interviews from the '90s where he explained that the Fallout team made games for each other, not for a target demographic. There was no pandering, no psychological manipulation — they put in things that made them laugh, things they'd always wanted to see in a game.
He acknowledges this philosophy had limits. With Arcanum, he admits he probably should have pulled back — he tried to squeeze every tabletop RPG idea he'd ever had into one game, and "some of them don't squeeze together so well."
Games Are Never Done, Only Shipped
Tim recalls Interplay tech director Jay Patel telling him around 1993: "Games are never done, only shipped." Over 30 years later, Tim confirms the truth of this. You never feel finished — you're either out of money, out of time, or you've done everything reasonable. Sometimes games ship with bugs and features you don't like because you're literally out of time, which really means out of money.
It's About the People
On reflection, Tim finds his "process" answer unsatisfactory. It's really about the team — the people. The experience of making a game together is "ineffable" and hard to explain to anyone who hasn't done it. His memories of Fallout aren't primarily about great features or brilliant ideas — they're about what the day-to-day was like, what he liked about working with each person.
He expresses sympathy for people who enter the industry solely to make money or to realize a specific game vision without considering who they'll make it with. For Tim, the "who" and the "how" matter more than the end product.
Losing People
After 42 years in the industry, Tim has inevitably lost touch with many colleagues, and increasingly, people he knew are passing away. He mentions:
- Scott Benny — producer and lead designer on Castles (1991), who also wrote for Fallout and came up with the name "Dogmeat." He died in 2022.
- Jennell Jaquays — legendary tabletop RPG designer whose Judges Guild modules (Dark Tower, Caverns of Thracia, The Unknown Gods) and Central Casting supplements were hugely influential on Tim's own tabletop campaigns and later game work. She passed away in January 2025. Tim met her once at GDC 2012 during his Fallout postmortem and hopes he didn't "fan boy out too much."
Tim's message: don't wait until people are gone to tell them how much they mean to you. "The clock is ticking, folks."
The Doorway Memory
Tim shares a story he says he's never told anyone before — a moment from late 1996 or early 1997, during the final stretch of Fallout development.
His office was at a T-intersection where the team's hallways met. One day he got up to do something, paused in his doorway, and started listening:
- To his right: Leonard Boyarsky and Jason Anderson were re-rendering something over and over, tweaking settings to make it look "just right" — something most players would never notice, but they noticed.
- To his left: Jason Suinn's office (the person who did all the lip syncing and coined the name "S.P.E.C.I.A.L.").
- Straight ahead: Jesse Reynolds and Chris Jones were in their office discussing C code — a data structure or algorithm.
- Further down: Fred Hatch, Nick Kesting, Scott Everts, and Chris Taylor.
Tim forgot what he'd gotten up to do. He just stood there for a couple of minutes, soaking it in, smiling. At the time, he was "like a child" — just in the experience without analyzing it. Looking back 28 years later, he realizes he was profoundly happy and content.
Nothing dramatic was happening. It was just his team — working hard, working well, making a game they all loved. Everyone had ownership. It wasn't deliberately designed to be that way; it was organic, a product of good people being good at what they did.
The Takeaway
Tim acknowledges this story might sound "dull" from the outside, but when he thinks about Fallout, he often thinks about that doorway moment. Behind everything was "the clicky-clack of keyboards, people doing scripts and code and art" — and it was ineffable.
His hope for anyone entering game development: that they get to experience something like that. A moment where you realize this right here, right now, is amazing — and that you remember it.
"With game development, it's kind of about the people and not even about the games."