Being Real

Abstract

Problem: Why does authenticity matter for a game developer sharing knowledge on YouTube, and what separates genuine content from performative content creation?

Approach: Tim Cain reflects on a friend's observation that his channel feels "real" β€” not an act β€” and explores what that means for his approach to sharing game development knowledge.

Findings: Being authentic β€” telling real stories from personal experience, avoiding outrage-bait and news cycles, and not performing a character β€” is what makes knowledge transfer most effective. The closest someone can get to understanding game development without doing it is hearing genuine stories from someone who lived them.

Key insight: Authenticity is the channel's foundation: real stories from real experience create the closest approximation of actually doing game development, and Tim's ultimate goal is to inspire viewers to make games themselves.

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

Not a Performance

Tim opens with a friend's observation: Tim's YouTube channel feels real. The friend knows Tim in person and confirms there's no act β€” the same passion, the same gesticulations, the same forgetting names of people and games and techniques like subsurface scattering. It's just Tim being Tim.

This surprised Tim at first. He assumed everyone just acts naturally on their channels. But his friend explained that many YouTubers and podcasters put on a front β€” acting over-the-top, artificially excited or angry for clicks. They dress differently, build elaborate sets, and have editing teams.

Tim films in his actual home office with his real working bookcase. He wears the same clothes he's about to go to work in. He does his own editing β€” very little of it β€” and records in single continuous unscripted takes.

This Isn't His Job

Despite his Wikipedia page now calling him a "YouTuber," Tim doesn't consider it his job. He's a game developer. That's what he does and what he gets paid for. The channel exists for one reason: to show viewers what game development is actually like.

What He Covers

  • Design β€” many different approaches, with focus on what worked for him, especially for RPGs
  • Production β€” best practices, scheduling, running team meetings
  • Code β€” discussed lightly, since there are many valid approaches
  • Not art or music β€” he acknowledges he can't speak to those disciplines and suggests those professionals should make their own channels

Stories Over Theory

Tim's approach has always been storytelling. When he taught at UC Irvine, students called his sessions "Tim Cain Story Hour." He came in on Thursdays while another professor taught Tuesdays. Students preferred Thursdays because the stories were real β€” things that actually happened.

He invokes the concept of qualia: you can't truly know what an apple tastes like until you eat one. Similarly, you can't fully understand game development until you do it. But the closest approximation is hearing genuine first-person stories from someone who lived through them.

A Personal Rule

Tim won't tell other developers' stories on his channel. Even when a game developer friend shared interesting experiences, Tim declined to retell them β€” they didn't happen to him. This constraint keeps the channel honest.

The Real Agenda

Tim's ultimate motivation is surprisingly simple: he wants viewers to become game developers and make games he can play.

His hoped-for progression:

  1. Viewer thinks "I can do this β€” if that guy can do it, I can do it"
  2. Some try Tim's approach: setting, story, mechanics process
  3. They make nonlinear games with multiple quest solutions, multiple endings, support for diverse character builds
  4. Tim gets to play those games

Avoiding the Outrage Cycle

Over two and a half years, viewers have regularly asked Tim to weigh in on controversies β€” Unity's pricing, movie scenes, game cutscenes. He consistently declines. His reasoning: those topics are ephemeral. He could list everything people asked him to cover and most viewers wouldn't even remember what those controversies were about.

He doesn't deliver news. He doesn't pretend to know what game development is β€” he tells you what it's actually like. Some viewers leave because of this, and Tim is fine with that.

Developing Your Own Voice

Tim acknowledges that many viewers disagree with his development methodologies. He's fine with that too. The important thing is that viewers who stick around will develop their own approaches, their own point of view, and ultimately make games that are unique to them.

The closing message: "I'm keeping it real, and so are you. So go out there and make Uncle Tim a game."

References