Get AI summaries of any video or article — Sign up free
Casey Muratori's Origin Story | The Standup thumbnail

Casey Muratori's Origin Story | The Standup

The PrimeTime·
5 min read

Based on The PrimeTime's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Jonathan Blow’s Jai compiler demos on Twitch—especially a compile-time game example—served as a catalyst for Muratori’s streaming ambitions.

Briefing

Casey Muratori’s path into streaming and long-form software teaching traces back to a single, high-impact demo: Jonathan Blow’s early “compile-time execution” work in Jai. Blow streamed compiler demos on Twitch—most notably a game-like example where compiling would actually play the game and bake results (like enemies killed before death) into the executable. That kind of “do real work at compile time” metaprogramming showcased what the language could do, and it helped normalize the idea that programming could be both expressive and practical.

Muratori credits that moment with nudging him toward trying Twitch himself. People who already knew his background—especially his “Witness Wednesdays” blog about what he was building in the game—started asking when he’d stream. With Blow’s Twitch activity as a visible precedent, Muratori decided to “try something,” which quickly became Handmade Hero: a long-running, engine-building series that walks viewers through the operating system layer, memory, rendering, bitmap loading, and other core mechanics in a hands-on way. Muratori admits he isn’t a natural game designer; his strength is building engines and systems, so the series focused on the foundational “how to make a program do these things” rather than on game design polish.

Handmade Hero’s popularity, Muratori says, wasn’t just entertainment—it filled a gap for programmers who found traditional learning paths too abstract and disconnected. For many viewers, the series offered a first real look at how low-level programming actually works: poking at the OS, understanding memory behavior, and reading file formats directly. He believes that for a certain class of developer, this was the missing on-ramp. The result wasn’t only more viewers building small projects; it was a pipeline of talent. At Better Software Conference, Muratori heard stories from attendees who started with Handmade Hero and then went on to build “absolutely insane” software—examples mentioned include File Pilot, plus later work that surprised him by scale and ambition.

That feedback changed Muratori’s mindset about his own output. After the conference, he considered producing a condensed version of the series—keeping the “straight line” learning path while cutting extraneous material like ray tracing that took many episodes and required extensive experimentation. He also described how Handmade Hero’s impact felt emotionally validating because his motivation has always been to make software “not suck as much.”

The origin story then widens into Muratori’s earlier programming formation: as a kid, he wanted to attend SIGGRAPH but faced an age restriction that barred him from the technical sessions. His father took him to the expo floor and the Film and Video Show instead, where he saw Pixar’s Knickknack short (premiered there) and other graphics research reels. Years later, his first real convention experience—GDC in the mid-to-late 1990s—reinforced the same feeling: being surrounded by people intensely serious about game programming. Muratori contrasts that with today’s more corporate, money-driven conference vibe, saying Better Software Conference briefly restored the earlier sense that programming is exciting again. The takeaway is that Muratori’s teaching career wasn’t accidental; it was catalyzed by a compile-time demo, then amplified by a learning format that made low-level software approachable—and by the community’s proof that it worked.

Cornell Notes

Casey Muratori traces his move toward streaming and teaching to Jonathan Blow’s early Jai compiler demos, especially a striking example where compiling could run a game and embed results into the executable. That Twitch visibility led viewers who knew Muratori’s prior work (Witness Wednesdays) to ask when he’d stream, prompting him to start Handmade Hero. Handmade Hero became popular because it demystified low-level programming—OS interaction, memory, rendering, and bitmap/file handling—at a level that many learners hadn’t seen before. Muratori says Better Software Conference brought confirmation that the series helped produce high-caliber builders, including people who went on to create major tools like File Pilot. The experience also pushed him to consider a condensed “straight line” version of the series, trimming long experiments like ray tracing.

What specific Jai demo helped kick off Muratori’s streaming origin story?

Jonathan Blow streamed compiler demos on Twitch, including a Jai example where compiling a game would actually play it. The compile process would run the game, count outcomes like enemies killed before death, and then stop and finish compilation—baking those results into the executable. Muratori highlights this as a concrete demonstration of running meaningful work at compile time, not just theoretical metaprogramming.

Why did Handmade Hero resonate with viewers beyond entertainment value?

Muratori says many programmers struggled to find a workable introduction to low-level systems programming. Handmade Hero showed the operating system layer, memory behavior, how to poke at those systems, and how to load and interpret bitmap data directly from files. For that audience, seeing the “first 30 episodes” as a guided path made it feel possible to start building immediately.

How did Muratori’s own strengths shape what Handmade Hero became?

Muratori openly says he can’t design games well. Instead, he focuses on engines and underlying systems. The series therefore emphasizes building the platform layer, rendering backend, and file/memory mechanics—so others can supply game design while he provides the technical foundation.

What feedback changed Muratori’s attitude after Handmade Hero?

At Better Software Conference, attendees told him they began with Handmade Hero and then went on to create major projects. Muratori describes hearing stories where people might not have made the leap without the series. He found that emotionally validating because his goal has long been to improve software quality, and the conference provided evidence that his teaching helped produce capable builders.

What does Muratori say he would change if he made a condensed follow-up?

He suggests a future condensed version that keeps the learning “straight line” and the hands-on feel, but removes extraneous or time-heavy experiments. He specifically notes that ray tracing and related work consumed a large fraction of the total episodes (described as roughly 100 out of 600), and he’d want such content either omitted or handled more controlled and efficiently.

How did early convention experiences influence Muratori’s view of programming culture?

As a child, he wanted to attend SIGGRAPH but couldn’t enter technical sessions due to an age rule; he could only access the expo floor and the Film and Video Show. Later, his first real convention experience at GDC (mid-to-late 1990s) felt energizing because most attendees were intensely serious about game programming. He contrasts that with modern conferences he views as more corporate, and says Better Software Conference briefly restored that earlier excitement.

Review Questions

  1. How does the compile-time Jai demo illustrate the broader theme of “what can be done at compile time,” and why was that persuasive to Muratori?
  2. Which parts of Handmade Hero does Muratori identify as the key learning breakthroughs for viewers, and what problem did those parts solve?
  3. What evidence from Better Software Conference changed Muratori’s thinking, and how did it affect his plans for a possible condensed series?

Key Points

  1. 1

    Jonathan Blow’s Jai compiler demos on Twitch—especially a compile-time game example—served as a catalyst for Muratori’s streaming ambitions.

  2. 2

    Handmade Hero emerged as a practical, systems-first learning series built around engine and platform fundamentals rather than game design.

  3. 3

    Muratori believes many learners needed an approachable on-ramp to low-level programming: OS interaction, memory, rendering, and direct file/bitmap handling.

  4. 4

    Handmade Hero’s influence extended beyond viewers building small projects; attendees reported going on to create major tools and advanced software.

  5. 5

    Better Software Conference provided Muratori with emotional validation that his teaching helped talented programmers take the next step.

  6. 6

    Muratori is considering a condensed future version that preserves the core learning path while cutting long, experimental sections like ray tracing.

  7. 7

    Muratori’s early exposure to SIGGRAPH’s Film and Video Show and later GDC attendance shaped his sense of what programming communities should feel like.

Highlights

A Jai demo where compiling a game actually plays it—and embeds results into the executable—made metaprogramming feel tangible, not abstract.
Handmade Hero’s biggest learning value came from showing low-level mechanics directly: OS layer, memory behavior, rendering pipelines, and bitmap/file parsing.
Muratori describes Better Software Conference as a turning point, with attendees crediting Handmade Hero for enabling them to build serious software afterward.
He wants a future condensed series that keeps the “straight line” learning experience while removing long experiments like ray tracing.

Topics

  • Jai Compile-Time Execution
  • Handmade Hero
  • Handmade Hero Streaming
  • Better Software Conference
  • SIGGRAPH Film and Video Show

Mentioned