Abstract
Problem: How do people in game development relate to their work, and how has this changed over the decades?
Approach: Tim Cain defines three categories — job, career, and calling — and traces how the proportions shifted across 43 years of industry history.
Findings: The early game industry was dominated by "calling" people due to high barriers to entry. As the industry professionalized in the '90s, career-oriented developers grew. By the 2010s, massive budgets and widespread layoffs pushed many from career into job mentality, causing experienced talent to leave the industry entirely.
Key insight: The shift from calling-dominated to job-dominated teams isn't new — it's a recurring cycle driven by industry economics — but understanding it as a lens helps developers make conscious choices about their own relationship to the work.
1. The Three Categories
Tim defines three distinct ways people relate to their work in game development:
Job people do their assigned tasks, collect their paycheck, and don't think about work outside of work hours. It doesn't define them. They work to support their life outside of work.
Career people do the same tasks but think bigger. They consider how their work fits into the whole product, plan where they want to be in 5, 10, or 20 years, and actively work to improve — taking classes, reading books, learning new skills outside of work hours. The key difference from job people is they think about their professional growth even when they're not at work.
Calling people do everything career people do, but the work is part of their identity. They think of themselves as game developers. They think about games and game design constantly — at work, at home, while walking the dog. They do it because they love it and get emotional fulfillment from it.
1.1. All Three Are Valid
Tim emphasizes that all three perspectives are justified. Job people rightly point out that companies don't care about you and job security is an illusion. Career people reasonably want to plan their professional trajectory. Calling people feel a compulsion to create that transcends practical concerns. None of these is objectively better or worse — it's subjective.
2. How The Proportions Changed Over Time
2.1. The 1980s: Calling Dominated
In the early days, there was a huge barrier to entry. Few game jobs existed, and getting hired required self-taught specialized knowledge — accessing video cards, optimizing frame rates — that mainstream programmers didn't have. The people who broke in were almost all calling people who had made active life decisions to pursue game development.
2.2. The 1990s: Careers Emerge
The industry grew, became more profitable and stable. Specialized roles crystallized — artist, designer, programmer, producer, QA. Books were published, schools began offering classes and then full degrees in game development. People could now plan a career path: "I want to get hired as a producer." The career proportion grew significantly.
2.3. The 2010s Onward: Jobs Take Over
Projects ballooned to tens or hundreds of millions of dollars. Huge companies formed, and with them came job insecurity — a hundred-million-dollar flop can't be recovered from easily. Career people who got laid off a few times stopped making 10-year plans. Many slipped from career mentality to job mentality. Meanwhile, teams of hundreds or thousands require many people to simply execute tasks without steering the ship — committee-designed games don't work, so most people on a large team are necessarily in a job role.
3. The Brain Drain
Tim observes experienced career people increasingly leaving the game industry entirely. Producers take their management skills to other entertainment fields or non-entertainment industries. Programmers leave for better-paying, more stable non-game programming jobs. This represents a significant loss of institutional knowledge.
3.1. But This Has Always Happened
Tim's key historical perspective: this cycle of talent loss isn't new. When the console market collapsed in the 1980s, mass layoffs drove people out. The same thing is happening now. It's never good — valuable experience is lost — but it's a recurring pattern across the industry's entire history. It happened before, it's happening now, and it will happen again.
4. The Nostalgia Factor
Tim admits he personally misses the early days when most of his colleagues were calling people. Development felt different — but he acknowledges this might be nostalgia. It might have felt different simply because teams were 15-30 people where everyone knew each other and could easily share feedback, rather than teams of hundreds or thousands where that kind of intimacy is structurally impossible.
5. A Lens, Not The Answer
Tim frames this entire job/career/calling distinction as one useful lens for understanding the game industry — not the only one. It offers a perspective that helps explain current industry dynamics as part of a longer historical pattern, and it invites developers to consciously examine their own relationship to their work.
6. References
- Tim Cain. YouTube video. https://www.youtube.com/watch?v=PuEdppkPjfo