School As Preparation For Game Development

High School: D&D and Foundational Skills

Tim's game development journey began in high school through Dungeons & Dragons. Playing regular campaigns with friends taught him several skills he'd use throughout his career:

• Group experience design — D&D is inherently collaborative, not solo. As a DM, Tim had to anticipate player choices, improvise new scenarios, and react on the fly.
• Entertainment-first philosophy — Tim gravitated toward DMing because he saw the DM's role as being an entertainer, not an adversary trying to kill the players. He embraced player creativity (like asking a vampire if they could become its thralls) rather than forcing them onto a predetermined path. This philosophy carried directly into his game design.
• DMs who insisted players follow the script lost the group's interest — a lesson about player agency that defined Tim's design career.

Academic Subjects That Stuck

• Geometry and trigonometry — Tim used sine, cosine, angle calculations, and tessellation knowledge for decades in game development.
• Creative writing and literature — Reading and discussing novels (including Homer's Odyssey) deepened his narrative thinking. His "little D&D brain" immediately recognized the quest structure in classical literature.

Undergraduate at UVA: Teams, Languages, and Hardware

Tim attended the University of Virginia's engineering school for computer science. The experience was formative in several areas:

Working in Teams

A major part of the engineering curriculum involved team projects, which taught Tim:

• Good communication is essential
• Some people don't pull their weight — sometimes you just have to do their work
• Not everyone is at the same level or good at the same things
• Learning to navigate these dynamics is a critical professional skill

The Robot Arm Project

One of Tim's favorite classes was an honors project building an automated factory. He was responsible for the robot arm, which required learning a new scripting language and dealing with physical hardware limitations like hysteresis (where a robot arm told to go forward and back wouldn't return to its exact starting position). The teamwork on this project was vital and memorable.

Programming Languages

Tim arrived at college knowing BASIC and C, but his education expanded dramatically:

• Learned Pascal, COBOL, Snobol, LISP, Prolog, and many others
• Crucially, learned why different languages exist — they're designed for different problem domains (string processing, numerical computation, etc.)
• This understanding of language design philosophy served him throughout his career

Mathematics

• Matrix math — proved essential when games went 3D (vectors, 3D matrix operations)
• Statistics — invaluable for analyzing focus group data, automated testing heat maps, identifying where players were dying and why, and determining whether character builds were well-supported
• Differential equations and applied math — broader mathematical fluency

Hardware Knowledge

As an engineering student, Tim took electrical and computer engineering classes where he physically built logic gates (OR, AND, NAND) on breadboards using wires, capacitors, and resistors. Understanding computing at this macro/physical level helped him think about code structure and optimization in ways he believes modern programmers may miss.

Lessons About People and Work Ethic

College also taught Tim hard lessons about human nature:

• Many students didn't treat college as an opportunity — they felt entitled to be there and assumed a cushy job would follow automatically.
• Self-deception about effort — A close friend claimed she worked harder than Tim because she was up until 1 AM. Tim pointed out that he did the homework right after class at 2 PM while she goofed around all afternoon. Same work, different discipline. She insisted her effort was "harder" simply because it was more stressful.
• Real consequences exist — A friend literally failed out of college, lost his scholarship, and had to leave. This scared Tim into taking his education seriously, especially since he was funding himself through student loans, work-study, and income from working at a game company.

Graduate School at UCI: Intelligence, AI, and Public Speaking

Tim earned a scholarship to study AI at UC Irvine and took it very seriously.

Encountering Truly Brilliant People

Grad school was Tim's first encounter with people operating on a fundamentally different intellectual level — people who could instantly grasp concepts, reduce complex equations, and see implications that took Tim much longer to parse. He learned not to be jealous of them but to appreciate working alongside them and following their lead.

Teaching and Public Speaking

As a teaching assistant (expected in grad school), Tim had to:

• Lecture in front of 300 people
• Run TA sessions explaining concepts multiple times in different ways
• Handle students who lacked foundational knowledge for advanced material

This experience directly prepared him for the communication demands of leading game development teams.

AI and Machine Learning

Tim had been interested in AI since undergrad, where he minored in Psychology specifically to take a graduate-level AI class (he begged the professor to let him in as an undergraduate). In grad school, he finally got to study neural networks, automata theory, and machine learning — his specialization.

LP MUDs: Early Games-as-a-Service

Grad school exposed Tim to LP MUDs (text-based multiplayer games), which were essentially games-as-a-service before the term existed. Programming content for people to play that same afternoon was exciting and taught him about multiplayer environments and live development.

Dealing with Skeptics

Many professors, grad students, and friends thought computer games were a waste of time and told Tim not to go into the industry. He went anyway. A few years later, his thesis adviser was asking him to come back and teach. Friends were asking how to get into the industry. Later still, they were asking how to get their kids in.

Tim's takeaway: people have a lot of opinions, and they're often wrong and unsupported.

The Moral: School Isn't the Only Path, But It's a Good One

Tim is explicit that school is not necessary for everyone and not the only way into game development. Making a demo remains a great way to get a job. However, school excels at teaching things that are hard to learn solo:

• Social skills — working with groups, understanding people, interacting professionally
• Communication — talking to people, presenting ideas, explaining concepts
• Project collaboration — working with others toward shared goals
• Technical foundations — math, programming, hardware understanding

For many people, it's simply easier to learn these skills in a structured educational environment than to try to acquire them independently.

References

• Tim Cain. YouTube video. https://www.youtube.com/watch?v=nWvwcH2IROo