Abstract
Problem: Why do outsiders and even industry veterans so often misjudge game developers' motivations?
Approach: Tim Cain reflects on his own career — from the passion-driven '80s and '90s through the industry's explosive growth in the 2000s — and shares a pivotal insight someone gave him about understanding other people's behavior.
Findings: People project their own motivations onto others. When someone accuses a developer of stealing code or letting success go to their head, it reveals what they would do in the same situation. Developer motivations have diversified over time — from pure passion, to career-building, to storytelling, to simply earning a paycheck — and all are valid.
Key insight: When someone tells you why a game developer did something, they're usually telling you what they would have done — not what actually happened.
The Early Days: Passion and Misfits
In the 1980s and '90s, game development didn't pay well, was considered weird and fringe, and most people entered the industry for one reason: they loved making games. It was a compulsion — "like this thing bursting out of them." A smaller group ended up in gamedev because they didn't fit anywhere else: misfits, social outcasts who gravitated toward a fringe industry. Tim notes that most early developers were both — passionate and odd.
When Tim decided to go into gamedev, friends, family, and teachers all told him: "You can do better. Do not do this." They meant something more fulfilling, more rewarding. But he had a passion, and he assumed everyone else in the industry shared it. He was mostly right — at the time.
The Interplay Source Code Story
Tim tells a revealing anecdote from when he left Interplay. They told him to destroy all his Fallout source code. He complied — wiped his hard drive, broke his CDs, ensured Interplay had the backed-up shipping version. He thought the matter was closed.
Years later, Interplay threatened him with a lawsuit, accusing him of taking the code. He invited them to Troika to inspect the Arcanum codebase. Their programmer looked through it, found nothing resembling Fallout code, and even remarked: "This is better." Tim's reaction: "Of course it's better. What programmer rewrites something and makes it worse?"
It turned out Interplay had simply lost their own copy of the source code. What confused Tim at the time was why they kept accusing him — until he received the key insight.
The Lens: People Project Their Own Motivations
Someone told Tim: "Stop thinking of people as doing things in terms of what you would do, and start thinking of their actions in terms of what they would do in your place."
This reframed everything. The people who accused Tim of stealing code were people who would have stolen it themselves. The person who thought Fallout's success was going to Tim's head? Success would have gone to theirs. The colleague who assumed Tim's master's degree made him feel superior? They would have lorded it over everyone.
Tim describes this as a moment when his entire career "snapped into focus." People don't accurately read others' motivations — they project their own.
The Industry Grows and Motivations Diversify
Something changed in the late '90s and accelerated in the 2000s. Game development became massive — bigger than TV, movies, and music combined. With that growth came people with motivations Tim hadn't encountered before:
Career-Builders
Some developers focused on their specialty rather than the game as a whole. A music composer wrote good music but didn't care about the game. An animation rigger rigged well but didn't know what the game was about. They optimized for their portfolio and career advancement, sometimes at the expense of the overall product. Tim found this confusing — previously, career advancement meant making good games.
Storytellers
A new generation saw games as a storytelling medium. Where Tim's parents' generation wanted to write "the great American novel," and his generation wanted to make "the great American movie," the new generation wanted to tell stories through games. Tim sees this as valid, but notes a problem: some want to lecture their story rather than tell it, which means removing player agency — "You can't say things back to these people. You can't do things. They're not wrong. You can't even interrupt them."
Paycheck Earners
Others saw gamedev simply as a tech job with tech pay. Tim explicitly validates this: "That is totally valid." He references his video on "Jobs, Careers, and Callings" — not every developer needs to have a calling, and the industry needs people at all levels of engagement.
Stop Guessing at Motives
Tim's conclusion is blunt: "Stop looking at people's motives. You're not good at it. I wasn't good at it." His approach now is to record only observable facts — "Bob said this, Mary did this" — without attributing motivations. Only the person themselves truly knows why they did what they did.
He compares the online discourse about developer motivations to how movies portray programmers as "hackers" — it's so wrong it's amusing. His brother, an accountant, has the same experience watching accounting scenes on TV. When you're outside a field, your assumptions about why practitioners do what they do are almost always wrong.
A boss once told Tim that making games was "no different than making shoes." Tim didn't respond — "When someone tells you something that's so wrong that it's not even correctable, you just have no response."
References
- Tim Cain. YouTube video. https://www.youtube.com/watch?v=s_K_jCJzQQI