Why Does Theo Make So Much Content About AI?

TL;DR

Theo makes so much AI content because he creates videos about whatever currently interests and excites him, not because he has abandoned programming. He estimates that conventional technical topics still make up roughly a third to half of his recent uploads, including databases, logging at scale, CSS, and parsing two billion rows. Read on to see how public conversations, Twitch, Twitter Spaces, and the T3 stack shaped this interest-driven approach.

Transcript

There's a comment I've been seeing a lot lately and I wanted to take the time to address it. He's usually in the format of something like, "Man, I missed the old Theo videos. I really liked when Theo would talk about tech and new frameworks and TypeScript, and now all he does is shill AI stuff that he makes money off of." I have a lot of thoughts a... Read More

Key Insights

• Theo's content choices are primarily driven by his current interests and excitement. He says he does little high-level planning around topic selection, so increased AI coverage reflects what he presently wants to investigate and discuss rather than a permanent rejection of web development.
• Traditional technical content still represents roughly a third to half of Theo's recent output. He cites detailed discussions of databases, Tailwind controversy, moving from Next to TanStack Start, application logging at scale, parsing two billion rows, and CSS as evidence that programming coverage continues.
• Lower audience interest can influence how technical uploads are perceived. Theo notes that his CSS video attracted little attention, which complicates the claim that viewers uniformly prefer his traditional programming content over the AI-related subjects appearing more frequently on the channel.
• Conversation is a tool Theo uses to form opinions, not merely present settled conclusions. He says his position at the beginning of a discussion can differ from his position at the end because talking through a subject and interacting with his Twitch chat helps him process it.
• Experienced coworkers helped Theo learn to balance excitement with skepticism. At Twitch, he discussed new frameworks, TypeScript changes, state-management libraries, and Elixir with more experienced developers who could challenge enthusiasm using their technical knowledge and institutional history.
• Twitter Spaces replaced some of the technical conversation Theo lost after leaving Twitch during COVID. He joined Jacob Evans's recurring Code and Life discussions despite having only about 40 or 50 followers, initially listening before becoming increasingly involved as a speaker.
• Video became necessary because some technical ideas could not be communicated effectively through audio alone. Theo first demonstrated his preferred tools by rewriting Jacob's project, then streamed the construction of a new application so viewers could see the stack, reasoning, and development speed directly.
• The T3 stack emerged from Theo's experiments while building Ping with a small, focused team. His chosen combination included Next.js, tRPC, Prisma, Tailwind, React, and TypeScript, while the name T3 originally referred to Theo and the three letters following the T.

Questions & Answers

Q: Why does Theo make so much content about AI?

Theo makes more AI content because AI currently interests and excites him. He says he does little high-level planning around topic selection, so the shift reflects what he wants to investigate and discuss at this time.

Q: Has Theo stopped making traditional programming videos?

No. Theo estimates that conventional technical material represents roughly a third to half of his recent videos, citing coverage of databases, Tailwind, moving from Next to TanStack Start, application logging at scale, parsing two billion rows, and CSS.

Q: Is Theo paid to promote AI instead of making coding content?

Theo presents his increased AI coverage as a result of his current interests, not as a calculated replacement for coding content. The transcript also includes a sponsored segment for Grapile, but his stated explanation for the broader shift is that he makes videos about what excites him.

Q: How did Theo's YouTube channel begin?

Theo says the account had existed for about 18 years and was originally used to watch YouTube. He uploaded one demonstration of filming skate footage with the iPhone 11 ultra-wide camera, but his later channel grew from wanting to discuss technical subjects rather than from an initial plan to become a YouTuber.

Q: Why were conversations with experienced developers important to Theo?

At Twitch, Theo discussed frameworks, TypeScript changes, state-management libraries, and Elixir with more experienced coworkers. Their knowledge and institutional history challenged his enthusiasm, helped him find a middle ground, and eventually taught him to represent both the excited and skeptical sides of a discussion.

Q: How does talking publicly help Theo form opinions?

Conversation is part of Theo's thinking process rather than just a way to present settled conclusions. He says his position can change during a discussion as he talks through the subject and responds to his Twitch chat.

Q: Why did Theo start explaining technology through video?

Audio conversations could not adequately demonstrate code or show how his preferred tools worked. After reducing Jacob Evans's roughly 5,000-line Firebase project to about 500 lines with his preferred stack, Theo streamed himself building another application from scratch so viewers could see the tools and reasoning directly.

Q: What is the T3 stack described by Theo?

Theo describes the T3 stack as Next.js, tRPC, Prisma, Tailwind, React, and TypeScript. It emerged from experiments while building Ping with a small, focused team, and the name originally referred to Theo and the three letters following the T.

Summary & Key Takeaways

• Theo responds to viewers who miss his earlier coverage of frameworks, TypeScript, and web development. He acknowledges that roughly a third to half of his recent uploads are conventional technical videos, while the rest concern AI, but argues that deep technical work remains present across database, logging, parsing, CSS, and framework discussions.

• The channel grew from Theo's need to discuss technologies that excited him after leaving Twitch during COVID. Twitter Spaces recreated conversations he once had with experienced coworkers, whose skepticism helped temper his enthusiasm. Speaking publicly became part of how he processed ideas, refined opinions, and developed more balanced technical judgments.

• Theo began making visual content because audio conversations could not adequately demonstrate code and tools. After simplifying Jacob Evans's 5,000-line Firebase project into a roughly 500-line application using his preferred stack, Theo streamed himself building another app from scratch. That demonstration established the interest-driven approach that still guides his channel.

• Key Insights_array_not_used_see_Key Insights