The Decline Of Generalists

tim-cain game-development team-structure specialization generalists production tools force-multiplier

Abstract

Problem: What is the single biggest change in game development over the last 40 years, and what has been lost because of it?

Approach: Tim Cain draws on his decades of experience shipping games — from the small teams of the 70s/80s to modern AAA — to trace how rising fidelity demands and team sizes have pushed the industry toward hyper-specialization.

Findings: Generalists (people skilled across multiple disciplines) have nearly vanished from game teams. While specialists are necessary for modern fidelity, their dominance has degraded tool quality, cross-discipline communication, and systemic cohesion in games. Features get built in vacuums and never connect to each other.

Key insight: Almost every "force multiplier" Cain ever worked with was a generalist — someone who could bridge disciplines, spot dependencies, and make everyone around them more productive. Their decline is one of the industry's most underappreciated losses.

Source: https://www.youtube.com/watch?v=_ihX2e9dnYM

What Is a Generalist?

A generalist is someone skilled in multiple disciplines. An artist who also writes narrative. A programmer who also designs systems. A producer who understands code and art pipelines. In the early days of the industry, most developers were generalists by necessity — teams were tiny, and one person wore many hats.

Today, what used to be "a game designer" has fractured into system designers, narrative designers, and level designers. "Programmer" has split into gameplay, UI, networking, graphics, and engine specialists. Even sound — once a single person doing music, effects, and UI audio — is now multiple specialized roles.

Why Specialists Took Over

Cain is clear that the rise of specialists makes sense. Modern games demand extraordinary fidelity — polygon counts, texture resolution, frame rate optimization, system depth, UX polish. The sheer volume of data and complexity requires people who go deep on one thing.

Teams are vastly larger. Development cycles are longer. The detail players expect is through the roof compared to the 70s and 80s. You need specialists. Some studios even have dedicated game-engine specialists — people whose entire job is understanding the quirks of Unreal or Unity (or, as Cain notes with self-aware humor, the quirks of his own engines).

Why Generalists Were (and Are) Great

Cross-Discipline Problem Solving

A generalist programmer who understands both UX and networking can design a multiplayer lobby interface that actually respects how the network code works — without needing a meeting full of specialists talking past each other. A programmer who deeply understands how art assets are constructed is the ideal person to build the particle system or optimize asset loading.

Cain gives a vivid example: a programmer who speaks musicians' language — who understands that sound designers want more than a cross-fade, who knows which controls to expose — produces fundamentally better audio integration than someone who just "hooks up Wwise and calls it done."

Tool Quality

This is Cain's biggest lament. No one makes tools better than generalists, because they understand what artists, musicians, and level designers are actually trying to do. They expose the right controls in clear, intuitive ways. Games are often only as good as their tools, and Cain directly links the decline of generalists to a decline in tool quality across the industry.

Designers and Artists Who Know Code

When non-programmers understand code, they can articulate precisely what they need instead of making vague requests. They understand engine limitations and work around them creatively, rather than constantly demanding the impossible and becoming frustrated. Cain contrasts these people favorably against those who "can't work under these conditions" when told a limitation can't be removed.

Producers Who Understand the Pipeline

A producer who understands code, art, and design is a better communicator and far better at spotting critical path issues. Cain describes producers who can look at a schedule and immediately see that animations are scheduled before their models are rigged — the kind of dependency that a non-technical producer would miss entirely.

Force Multipliers

Cain invokes a concept he's used in previous videos: the force multiplier — someone whose presence on a team improves everyone's productivity. Almost every force multiplier he's known was a generalist. They multiply force by:

  • Stepping in when two specialists are talking past each other and facilitating communication
  • Noticing something in the game and proactively exposing functionality to make others' work easier
  • Looking at a tool and seeing how it could be restructured to better serve its users
  • Connecting systems that were built in isolation

The Cost of Losing Generalists

Without generalists, Cain sees recurring problems in modern games:

  • Tools aren't as good as they could be — built by specialists who don't fully understand the end user's workflow
  • Developers talk past each other — no one bridges the language gap between disciplines
  • Features built in vacuums — individual systems are well-crafted but disconnected. "I love this feature but I never use it" — crafting systems that don't matter in combat, mechanics that are fun in isolation but irrelevant to the larger game
  • No connective tissue — passionate specialists build great individual pieces, but nobody weaves them into a coherent whole

Advice for Aspiring Developers

Cain closes with a note to people entering the industry: he was always on the lookout for a good generalist, even though nobody really sells themselves that way. The tell is when teammates say "I love working with her — she knows how to talk my language." What they're really saying is: that person is a generalist, and they're invaluable.

References