Passivity

Defining Passivity

Tim defines passivity as working with zero passion — going with the flow, not caring much about any particular feature, direction, or outcome. He distinguishes this from his earlier video on passion: people don't announce "I'm really passive," they just act that way. Similarly, passionate people don't usually declare their passion — others notice it.

He frames this video as the opposite of his discussions on passion, referencing his work-life balance and jobs/careers/callings videos.

Passivity Is Acceptable — With Limits

Tim is explicit that he's perfectly fine with passive people. In his jobs/careers/callings framework, passive workers ("jobs people") are completely necessary to the process. They come in, do their work, and leave. They don't question the fundamental direction of the game, which is fine — that's what a game director is for.

The Fallout team was special because it had a ton of passionate people who all agreed on the same direction. But not every team needs that; a mix of temperaments works.

The core problem: passive people often want to make the problems their passivity causes into other people's problems. That's where Tim draws the line.

The Moving Day Story

When Tim was 29, he moved from an apartment to his first house. He prepared meticulously: packed dishes, glassware, computer equipment, personal papers, and banking documents himself over multiple trips. On moving day, friends only needed to help with furniture that required two people — a bed, mattress, couch. The whole move took about two and a half hours. Everyone was eating pizza by 12:30 and had the afternoon free.

A few months later, a friend asked for the same help. They arrived to find him still packing, without enough boxes. Someone had to run out and buy more. Eight hours later, at 6 PM, they were still working, hungry and grumpy. When confronted about his lack of preparation, the friend turned it around: "I helped you all move" and "You're not really my friends." His passivity — failing to prepare — became everyone else's problem.

The Tabletop RPG Problem

Tim, who frequently serves as DM/GM, describes players who wanted to play but put in zero effort. They showed up without:

• The player's handbook (or even a free PDF on their phone)
• Dice
• Paper and pencil

They wanted everything provided to them, not recognizing that the DM had already invested substantial preparation time. When other players got frustrated, these passive players were baffled: "I'm just playing here. What are you getting so mad at me for?" Their passivity became everyone else's problem, and they were shocked when they weren't invited back.

The University Project Class

Tim references his "Crunch Part Two" video about a software engineering class in his final undergraduate year. The entire grade was one project assigned the first week. The professor explicitly warned students to start immediately.

Most of the class waited. Most didn't finish. Most failed. They complained it was unfair — not enough time, too hard, other classes got in the way. Meanwhile, Tim and a few others who started week one finished with time to spare (it took him 13 of 15 weeks). The professor was frustrated too — he'd warned them, and they ignored him, figuring they could knock it out in a couple of weeks.

These students couldn't claim they weren't warned. They couldn't claim ignorance of the stakes. They simply didn't do it — and then made it someone else's problem.

Weaponized Ignorance in the Industry

Tim has seen passivity at all levels of the game industry. He describes co-workers who used what he calls "weaponized ignorance" — pretending they weren't good at assigned tasks they didn't want to do, claiming "this isn't my area of specialty." He's 99% sure one programmer deliberately specialized in a narrow area specifically to avoid all the work he didn't like.

Tim notes he personally dislikes UI programming but did it in almost all his games because other programmers refused, saying "I don't want to do that" or "I'm not very good at it."

He also saw this from managers. One manager was extremely picky about how Tim ran his project — demanding documents, processes, and structure. When that same manager was assigned his own project, he didn't follow any of his own advice. The project failed. Tim realized there's a big difference between telling people what to do and actually doing it yourself.

The YouTube Channel Parallel

Tim extends the pattern to his own audience. People in his comments ask him to teach code or walk through designs in detail, despite hundreds of other channels already doing that. He points out the abundance of free resources: free engines, free art, free code samples, and cheap foundational starter projects for any game type.

The number one question on his channel used to be how to get a job. He made a video about it. Making a demo has never failed to be good advice for job seekers — and yet people still don't do it. They say they want to make games but they don't make games. What they make are excuses.

The Core Message

Tim's closing argument is direct: if you're being passive, that is on you. Whether at home, school, work, or in life — there's so much you're capable of doing. But to do a lot, you've got to first do a little. You've got to get started.

As he steps away from the industry, he wants new people to step in. The industry needs passionate people, but it can also use passive people — as long as that passivity doesn't become other people's problems.