AI Engineer World's Fair 2026

The Highest Loop — swyx

Read the talk

The Highest Loop

swyx connects the work of choosing an AI system’s level of abstraction to the human work of gathering, deciding what to build next, and carrying those decisions back into teams and daily life.

From a talk by Shawn "swyx" Wang

At a glance

Ideas worth remembering

  • Choosing the right abstraction is part of AI engineering: move upward to pursue productivity and inference scale, and downward to diagnose reliability problems.

  • Use the conference’s tracks to address the level where you work or the level where you are blocked.

  • The highest loop is collective work that decides what loops to create next; its practical result should travel back into teams and personal workflows.

From tokens to scheduled work

A token, a chat, a tool call, a goal, an automation: swyx opens his AI Engineer World’s Fair address by moving through increasingly broad units of AI work. The progression reaches cron jobs and software factories, where the concern extends beyond an individual response to repeated activity and the organization of that activity. He calls this “loop stacking.”

The sequence deliberately skips steps. Its purpose is to introduce a question that survives changes in tools: which loop are you working in? The essay he names, Loopcraft, gives that question a home. Here, the core engineering skill is recognizing the current level of abstraction and deciding whether it is the useful place to work.

1:051:10
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

1:05 · section reference included

Move up for scale, down for reliability

The practical decision has two directions, each serving a different need:

  • Move up when ready to scale. Work at the next level of abstraction to pursue greater productivity and scale inference. The unit of attention becomes a broader loop.
  • Move down when something breaks. Return to a lower level to investigate reliability and fix the bugs that the broader view leaves unresolved.

“A stack of while loops” is the programmer’s analogy. It makes movement between levels feel ordinary: engineers, leaders, researchers and founders all need to reason within a loop and step into or out of it. This is an organizing model for work; the address does not supply a software architecture or a test for when a system is ready to move upward.

That model also explains the conference’s abundance of tracks. “I’m not gonna apologize for good content,” swyx says. The attendee’s job is to route themselves toward the level where they currently work or where they are blocked. Choosing a session becomes a practical version of choosing an abstraction: find the material that addresses the problem at its useful level.

1:582:28
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

1:58 · section reference included

The human analogy expands from heartbeat to collective work

The human version begins with a heartbeat, then expands through speech, tool use and work: “eat, sleep, code, repeat,” with prompting offered as an update. Teams, small groups and families widen the frame again. Tiny teams matter here because they place individual activity inside a shared undertaking.

The analogy then reaches beyond personal, family, company and national contexts to collective intelligence and the human projects those groups contribute to. The question changes from how an individual repeats useful work to where that work is taking everyone. This is a proposed way to think about coordination and purpose, rather than a claim that human life literally executes like a program.

The conference program gives that expansion a concrete expression. Healthcare, finance, go-to-market and forward-deployed engineering receive tracks as AI work spreads beyond coding. swyx presents this as agents generalizing across domains; the tracks show the intended scope of that exploration, without establishing how reliably a capability transfers from one domain to another.

2:583:28
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

2:58 · section reference included

The organizers’ stress curves

The address briefly returns from civilization-scale coordination to the very human problem of selling conference tickets. The first AI Engineer event in 2023 had a sales curve swyx describes as roughly linear. The first World’s Fair in 2024 brought about 2,000 people. For the current event, he corrects his initial figure: the target was 6,000, and the total had crossed 7,000 that day.

What do the sales curves reveal about when people commit? That is the useful comparison behind the joke about organizers’ “stress curves.” Earlier ticket purchases had been requested, but purchases had become more concentrated instead. swyx describes the Gini coefficient as rising—“the wrong direction”—and asks attendees to join earlier next time. No coefficient values or calculation details are given, so the supported lesson is about the reported concentration of buying, rather than its numerical size.

4:595:30
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

4:59 · section reference included

The loop that makes loops

Why put this work into a conference? The closing definition supplies the title: the highest loop is where humans gather to figure out what the next loop should be. “The loop that makes loops” puts the choice of future work inside a collective activity. A gathering earns its place when it helps people decide what processes to create next.

AI Engineer’s summits give that idea an organizational form. swyx names New York, Paris, Singapore, Melbourne and Miami, describes organizing with partners, and invites people to organize in their home countries with help from a partnerships team. He calls the World’s Fair the “summit of summits”: a gathering that brings the wider network together.

The final request is to carry something home: find a generative process for creating loops, then propagate it into teams, personal workflows and life. The intended output of the gathering is a way to keep choosing and creating useful work after the event ends.

5:306:00
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

6:00 · section reference included

Transcript download
Read the transcript and explore slides

Loading transcript and slides…