read-only demo

Videos RjfbvDXpFls

Building pi in a World of Slop — Mario Zechner

index_state ready data_status ok

AI Engineer· published 2026-04-16· 0:18:25· en-US· indexed 2026-08-10 19:33

Open on YouTube

Scene timeline

  1. Shot 0, 0:00 to 0:05, 1 of 1 keyframes kept
  2. Shot 1, 0:05 to 0:09, 1 of 1 keyframes kept
  3. Shot 2, 0:09 to 0:15, 1 of 1 keyframes kept
  4. Shot 3, 0:15 to 0:16, 1 of 1 keyframes kept
  5. Shot 4, 0:16 to 0:29, 1 of 1 keyframes kept
  6. Shot 5, 0:29 to 0:31, 1 of 1 keyframes kept
  7. Shot 6, 0:31 to 0:44, 1 of 1 keyframes kept
  8. Shot 7, 0:44 to 0:47, 1 of 1 keyframes kept
  9. Shot 8, 0:47 to 0:50, 1 of 1 keyframes kept
  10. Shot 9, 0:50 to 1:01, 1 of 1 keyframes kept
  11. Shot 10, 1:01 to 1:02, 1 of 1 keyframes kept
  12. Shot 11, 1:02 to 1:13, 1 of 1 keyframes kept
  13. Shot 12, 1:13 to 1:15, 1 of 1 keyframes kept
  14. Shot 13, 1:15 to 1:31, 1 of 1 keyframes kept
  15. Shot 14, 1:31 to 1:40, 1 of 1 keyframes kept
  16. Shot 15, 1:40 to 1:42, 1 of 1 keyframes kept
  17. Shot 16, 1:42 to 1:45, 1 of 1 keyframes kept
  18. Shot 17, 1:45 to 1:47, 1 of 1 keyframes kept
  19. Shot 18, 1:47 to 1:54, 1 of 1 keyframes kept
  20. Shot 19, 1:54 to 1:57, 1 of 1 keyframes kept
  21. Shot 20, 1:57 to 2:09, 1 of 1 keyframes kept
  22. Shot 21, 2:09 to 2:31, 1 of 1 keyframes kept
  23. Shot 22, 2:31 to 2:36, 1 of 1 keyframes kept
  24. Shot 23, 2:36 to 2:38, 1 of 1 keyframes kept
  25. Shot 24, 2:38 to 3:06, 1 of 1 keyframes kept
  26. Shot 25, 3:06 to 3:34, 1 of 1 keyframes kept
  27. Shot 26, 3:34 to 3:46, 1 of 1 keyframes kept
  28. Shot 27, 3:46 to 3:55, 1 of 1 keyframes kept
  29. Shot 28, 3:55 to 4:16, 1 of 1 keyframes kept
  30. Shot 29, 4:16 to 4:21, 1 of 1 keyframes kept
  31. Shot 30, 4:21 to 4:29, 1 of 1 keyframes kept
  32. Shot 31, 4:29 to 4:32, 1 of 1 keyframes kept
  33. Shot 32, 4:32 to 4:42, 1 of 1 keyframes kept
  34. Shot 33, 4:42 to 4:44, 1 of 1 keyframes kept
  35. Shot 34, 4:44 to 4:47, 1 of 1 keyframes kept
  36. Shot 35, 4:47 to 4:56, 1 of 1 keyframes kept
  37. Shot 36, 4:56 to 4:59, 1 of 1 keyframes kept
  38. Shot 37, 4:59 to 5:13, 1 of 1 keyframes kept
  39. Shot 38, 5:13 to 5:18, 1 of 1 keyframes kept
  40. Shot 39, 5:18 to 5:24, 1 of 1 keyframes kept
  41. Shot 40, 5:24 to 5:30, 1 of 1 keyframes kept
  42. Shot 41, 5:30 to 5:39, 1 of 1 keyframes kept
  43. Shot 42, 5:39 to 5:56, 1 of 1 keyframes kept
  44. Shot 43, 5:56 to 6:01, 1 of 1 keyframes kept
  45. Shot 44, 6:01 to 6:19, 1 of 1 keyframes kept
  46. Shot 45, 6:19 to 6:26, 1 of 1 keyframes kept
  47. Shot 46, 6:26 to 6:56, 1 of 1 keyframes kept
  48. Shot 47, 6:56 to 7:00, 1 of 1 keyframes kept
  49. Shot 48, 7:00 to 7:03, 1 of 1 keyframes kept
  50. Shot 49, 7:03 to 7:04, 1 of 1 keyframes kept
  51. Shot 50, 7:04 to 7:26, 1 of 1 keyframes kept
  52. Shot 51, 7:26 to 7:42, 1 of 1 keyframes kept
  53. Shot 52, 7:42 to 7:44, 1 of 1 keyframes kept
  54. Shot 53, 7:44 to 7:56, 1 of 1 keyframes kept
  55. Shot 54, 7:56 to 8:01, 1 of 1 keyframes kept
  56. Shot 55, 8:01 to 8:28, 1 of 1 keyframes kept
  57. Shot 56, 8:28 to 8:54, 1 of 1 keyframes kept
  58. Shot 57, 8:54 to 9:21, 0 of 1 keyframes kept
  59. Shot 58, 9:21 to 9:31, 1 of 1 keyframes kept
  60. Shot 59, 9:31 to 9:40, 1 of 1 keyframes kept
  61. Shot 60, 9:40 to 9:43, 1 of 1 keyframes kept
  62. Shot 61, 9:43 to 9:52, 1 of 1 keyframes kept
  63. Shot 62, 9:52 to 9:53, 1 of 1 keyframes kept
  64. Shot 63, 9:53 to 9:55, 1 of 1 keyframes kept
  65. Shot 64, 9:55 to 9:57, 1 of 1 keyframes kept
  66. Shot 65, 9:57 to 9:58, 1 of 1 keyframes kept
  67. Shot 66, 9:58 to 10:09, 1 of 1 keyframes kept
  68. Shot 67, 10:09 to 10:10, 1 of 1 keyframes kept
  69. Shot 68, 10:10 to 10:23, 1 of 1 keyframes kept
  70. Shot 69, 10:23 to 10:24, 1 of 1 keyframes kept
  71. Shot 70, 10:24 to 10:28, 1 of 1 keyframes kept
  72. Shot 71, 10:28 to 10:34, 1 of 1 keyframes kept
  73. Shot 72, 10:34 to 10:45, 1 of 1 keyframes kept
  74. Shot 73, 10:45 to 10:48, 1 of 1 keyframes kept
  75. Shot 74, 10:48 to 10:57, 1 of 1 keyframes kept
  76. Shot 75, 10:57 to 10:58, 1 of 1 keyframes kept
  77. Shot 76, 10:58 to 11:00, 1 of 1 keyframes kept
  78. Shot 77, 11:00 to 11:04, 1 of 1 keyframes kept
  79. Shot 78, 11:04 to 11:07, 1 of 1 keyframes kept
  80. Shot 79, 11:07 to 11:10, 1 of 1 keyframes kept
  81. Shot 80, 11:10 to 11:11, 1 of 1 keyframes kept
  82. Shot 81, 11:11 to 11:13, 1 of 1 keyframes kept
  83. Shot 82, 11:13 to 11:36, 1 of 1 keyframes kept
  84. Shot 83, 11:36 to 11:38, 1 of 1 keyframes kept
  85. Shot 84, 11:38 to 11:44, 1 of 1 keyframes kept
  86. Shot 85, 11:44 to 11:52, 1 of 1 keyframes kept
  87. Shot 86, 11:52 to 11:58, 1 of 1 keyframes kept
  88. Shot 87, 11:58 to 12:05, 1 of 1 keyframes kept
  89. Shot 88, 12:05 to 12:06, 1 of 1 keyframes kept
  90. Shot 89, 12:06 to 12:07, 1 of 1 keyframes kept
  91. Shot 90, 12:07 to 12:17, 1 of 1 keyframes kept
  92. Shot 91, 12:17 to 12:24, 1 of 1 keyframes kept
  93. Shot 92, 12:24 to 12:26, 1 of 1 keyframes kept
  94. Shot 93, 12:26 to 12:30, 0 of 1 keyframes kept
  95. Shot 94, 12:30 to 12:54, 1 of 1 keyframes kept
  96. Shot 95, 12:54 to 12:57, 1 of 1 keyframes kept
  97. Shot 96, 12:57 to 13:03, 1 of 1 keyframes kept
  98. Shot 97, 13:03 to 13:14, 1 of 1 keyframes kept
  99. Shot 98, 13:14 to 13:21, 1 of 1 keyframes kept
  100. Shot 99, 13:21 to 13:28, 1 of 1 keyframes kept
  101. Shot 100, 13:28 to 13:46, 1 of 1 keyframes kept
  102. Shot 101, 13:46 to 13:48, 1 of 1 keyframes kept
  103. Shot 102, 13:48 to 13:56, 1 of 1 keyframes kept
  104. Shot 103, 13:56 to 13:58, 1 of 1 keyframes kept
  105. Shot 104, 13:58 to 14:15, 1 of 1 keyframes kept
  106. Shot 105, 14:15 to 14:23, 1 of 1 keyframes kept
  107. Shot 106, 14:23 to 14:38, 1 of 1 keyframes kept
  108. Shot 107, 14:38 to 15:09, 1 of 1 keyframes kept
  109. Shot 108, 15:09 to 15:22, 1 of 1 keyframes kept
  110. Shot 109, 15:22 to 15:28, 1 of 1 keyframes kept
  111. Shot 110, 15:28 to 15:35, 1 of 1 keyframes kept
  112. Shot 111, 15:35 to 15:48, 1 of 1 keyframes kept
  113. Shot 112, 15:48 to 15:49, 0 of 1 keyframes kept
  114. Shot 113, 15:49 to 16:05, 1 of 1 keyframes kept
  115. Shot 114, 16:05 to 16:11, 1 of 1 keyframes kept
  116. Shot 115, 16:11 to 16:13, 1 of 1 keyframes kept
  117. Shot 116, 16:13 to 16:27, 1 of 1 keyframes kept
  118. Shot 117, 16:27 to 16:55, 1 of 1 keyframes kept
  119. Shot 118, 16:55 to 17:33, 1 of 1 keyframes kept
  120. Shot 119, 17:33 to 17:34, 1 of 1 keyframes kept
  121. Shot 120, 17:34 to 17:38, 1 of 1 keyframes kept
  122. Shot 121, 17:38 to 17:45, 1 of 1 keyframes kept
  123. Shot 122, 17:45 to 18:09, 1 of 1 keyframes kept
  124. Shot 123, 18:09 to 18:10, 1 of 1 keyframes kept
  125. Shot 124, 18:10 to 18:24, 1 of 1 keyframes kept
  126. Shot 125, 18:24 to 18:24, 0 of 1 keyframes kept

126 shot(s).

keyframes kept every frame deduplicated

What was stored

cues
279
whisperx 279
chunks
33
from 279 cues
keyframes
122
kept of 126 captured
frames with text
122
3,772 lines read
chapters
11
from the source metadata
keyframe bytes
14.7 MB
word timings on 279 cues

Provenance

Each pipeline stage, its state and the model that produced it
stage state model started took
fetch done 2026-08-09 20:57 0s
stt done 2026-08-09 20:57 37s
chunk done 2026-08-09 20:57 0s
text_embed done 2026-08-10 19:33 1s
keyframe done 2026-08-08 20:36 4m 27s
ocr done 2026-08-08 20:41 1m 16s
frame_embed done 2026-08-10 19:33 21s

Frames, and what the machine read

  • 0:03 #0 done2 line(s)

    shot 0·sharpness 658.4

    1. AlEngineer0.98
    2. EUROPE1.00
  • 0:08 #1 done2 line(s)

    shot 1·sharpness 829.1

    1. PRESENTINGSPONSOR1.00
    2. Google DeepMind1.00
  • 0:12 #2 done3 line(s)

    shot 2·sharpness 907.7

    1. PLATINUM SPONSORS0.98
    2. # Braintrust0.96
    3. WorkOS OpenAI0.95
  • 0:15 #3 done5 line(s)

    shot 3·sharpness 252.2

    1. -OR0.74
    2. tone0.97
    3. I love0.87
    4. @EnoRe0.84
    5. Mexhorthy0.81
  • 0:27 #4 done19 line(s)

    shot 4·sharpness 1549.5

    1. 18:480.89
    2. EUROPE1.00
    3. EARENDIL1.00
    4. Mind1.00
    5. Building pi in a World of Slop1.00
    6. P0.94
    7. exhorthy0.92
    8. PI.DEV1.00
    9. gine0.98
    10. A TRAGEDY IN 3 ACTS0.95
    11. MARIO ZECHNER· @BADLOGICGAMES0.98
    12. AI ENGINEER EUROPE APRIL 10, 20260.97
    13. AlEngineer0.99
    14. BUILDING PI IN A WORLD OF SLOP1.00
    15. EUROPE1.00
    16. PRESENTED BY1.00
    17. Google DeepMind1.00
    18. MARIO ZECHNER / Creator0.97
    19. F0.79
  • 0:29 #5 done26 line(s)

    shot 5·sharpness 1269.7

    1. 18:500.94
    2. EUROPE1.00
    3. EARENDIL0.99
    4. oogle De0.94
    5. AIEngir0.92
    6. EUROPE1.00
    7. AlEn0.93
    8. nec0.96
    9. EUI0.78
    10. Act I1.00
    11. thorthy0.90
    12. Wc0.81
    13. AlEngir0.92
    14. BUILDING PI1.00
    15. EUROPE1.00
    16. AlEngine0.96
    17. So0.84
    18. MARIO ZECHNER· @BADLOGICGAMES0.97
    19. AI ENGINEER EUROPE APRIL 10, 20260.97
    20. AlEngineer0.98
    21. BUILDING PI IN A WORLD OF SLOP0.99
    22. EUROPE1.00
    23. PRESENTED BY1.00
    24. Google DeepMind1.00
    25. MARIO ZECHNER / Creator0.97
    26. F0.74
  • 0:39 #6 done24 line(s)

    shot 6·sharpness 1836.8

    1. 11:900.95
    2. EUROPE1.00
    3. EARENDIL1.00
    4. Goo0.99
    5. ind1.00
    6. AIEn0.94
    7. In the beginning0.98
    8. ne0.98
    9. there was Caude Čode0.94
    10. AIEn0.88
    11. (WELL ACTUALLY, COPY AND PASTE FROM CHATGPT, THEN GITHUB COPILOT1.00
    12. EU1.00
    13. TAB TAB TAB, THEN AIDER, THEN CURSOR)1.00
    14. Al0.77
    15. inee0.99
    16. MARIO ZECHNER· @BADLOGICGAMES0.97
    17. AI ENGINEER EUROPE APRIL 10, 20260.98
    18. AlEngineer0.97
    19. BUILDING PI IN A WORLD OF SLOP0.97
    20. EUROPE1.00
    21. PRESENTED BY1.00
    22. Google DeepMind1.00
    23. MARIO ZECHNER/Creator1.00
    24. F0.72
  • 0:45 #7 done18 line(s)

    shot 7·sharpness 1428.1

    1. 11:860.98
    2. EUROPE1.00
    3. EARENDIL1.00
    4. Go1.00
    5. 1ind0.88
    6. AIE1.00
    7. Love the Claude Code team1.00
    8. AIE1.00
    9. jine0.99
    10. MARIO ZECHNER · @BADLOGICGAMES0.97
    11. AI ENGINEER EUROPE APRIL 10, 20260.96
    12. AlEngineer0.98
    13. BUILDING PI IN A WORLD OF SLOP0.99
    14. EUROPE1.00
    15. PRESENTED BY1.00
    16. Google DeepMind1.00
    17. MARIO ZECHNER / Creator0.99
    18. F0.78
  • 0:50 #8 done16 line(s)

    shot 8·sharpness 1411.4

    1. 11:111.00
    2. EUROPE0.99
    3. EARENDIL1.00
    4. Go1.00
    5. 1ind0.98
    6. Love the Claude Code team1.00
    7. jine0.89
    8. MARIO ZECHNER· @BADLOGICGAMES0.98
    9. AI ENGINEER EUROPE · APRIL 10, 20260.95
    10. AlEngineer0.98
    11. BUILDING PI IN A WORLD OF SLOP0.99
    12. EUROPE1.00
    13. PRESENTED BY1.00
    14. Google DeepMind1.00
    15. MARIO ZECHNER / Creator0.96
    16. P0.67
  • 0:56 #9 done18 line(s)

    shot 9·sharpness 1784.7

    1. 11:171.00
    2. EARENDIL1.00
    3. norkel1.00
    4. Love the Claude Code team0.98
    5. They created the entire genre1.00
    6. Dumb0.88
    7. Not a roast. Just why I moved on0.99
    8. Zone0.99
    9. icrosoft0.99
    10. MARIO ZECHNER · BBADLOGICGAMES0.97
    11. AI ENGINEER EUROPE APRIL 10, 20261.00
    12. AlEngineer0.94
    13. BUILDING PI IN A WORLD OF SLOP0.97
    14. EUROPE1.00
    15. PRESENTED BY1.00
    16. Google DeepMind1.00
    17. MARIO ZECHNER / Creator0.99
    18. F0.86
  • 1:01 #10 done17 line(s)

    shot 10·sharpness 1493.2

    1. 11:221.00
    2. EARENDIL1.00
    3. Simple, predictable,0.99
    4. π1.00
    5. fit my workflow0.99
    6. intone1.00
    7. Dugmb0.87
    8. Zone1.00
    9. MARIO ZECHNER· @BADLOGICGAMES0.98
    10. AI ENGINEER EUROPE APRIL 10, 20260.98
    11. AlEngineer0.98
    12. BUILDING PI IN A WORLD OF SLOP0.98
    13. EUROPE1.00
    14. PRESENTED BY1.00
    15. Google DeepMind1.00
    16. MARIO ZECHNER / Creator0.98
    17. F0.72
  • 1:06 #11 done21 line(s)

    shot 11·sharpness 1599.5

    1. 11:271.00
    2. EARENDIL1.00
    3. AlEngineer0.98
    4. EUROPE0.98
    5. Snor0.93
    6. Simple, predictable,0.98
    7. AlEngine0.96
    8. fit my workflow0.99
    9. EUROPE0.93
    10. Zone0.99
    11. Microsof0.97
    12. AlEngineer0.97
    13. MARIO ZECHNER· @BADLOGICGAMES0.98
    14. AI ENGINEER EUROPE APRIL 10, 20260.96
    15. AlEngineer0.99
    16. BUILDING PI IN A WORLD OF SLOP0.97
    17. EUROPE1.00
    18. PRESENTED BY1.00
    19. Google DeepMind1.00
    20. MARIO ZECHNER / Creator0.97
    21. F0.92
  • 1:14 #12 done22 line(s)

    shot 12·sharpness 1600.5

    1. 11:351.00
    2. EARENDIL1.00
    3. Engineer1.00
    4. EUROPE0.99
    5. Snork1.00
    6. Simple, predictable,0.98
    7. Engine0.99
    8. fit my workflow0.98
    9. EUROPE0.97
    10. xhorthy1.00
    11. Microsot0.97
    12. Engineer1.00
    13. EUROPE1.00
    14. MARIO ZECHNER· @BADLOGICGAMES0.97
    15. AI ENGINEER EUROPE APRIL 10, 20260.97
    16. AlEngineer0.98
    17. BUILDING PI IN A WORLD OF SLOP0.97
    18. EUROPE1.00
    19. PRESENTED BY1.00
    20. Google DeepMind1.00
    21. MARIO ZECHNER / Creator0.97
    22. F0.78
  • 1:17 #13 done24 line(s)

    shot 13·sharpness 1403.0

    1. 11:381.00
    2. But then1.00
    3. EARENDIL1.00
    4. Engineer0.93
    5. EUROPE1.00
    6. Snorke!0.95
    7. Engineer0.93
    8. EUROPE1.00
    9. Dumb0.98
    10. Zone0.99
    11. Micros1.00
    12. Engineer1.00
    13. EUROPE1.00
    14. MARIO ZECHNER1.00
    15. @BADLOGICGAMES0.96
    16. AI ENGINEER EUROPE1.00
    17. APRIL 10, 20260.98
    18. AlEngineer0.98
    19. BUILDING PI IN A WORLD OF SLOP0.97
    20. EUROPE1.00
    21. PRESENTED BY1.00
    22. Google DeepMind1.00
    23. MARIO ZECHNER / Creator0.97
    24. F0.84
  • 1:34 #14 done21 line(s)

    shot 14·sharpness 1396.5

    1. 11:551.00
    2. EUROPE1.00
    3. But then0.99
    4. EARENDIL1.00
    5. Googl0.94
    6. AIEI0.97
    7. @Enode0.66
    8. AIE1.00
    9. AIEr0.94
    10. er1.00
    11. MARIO ZECHNER1.00
    12. @BADLOGICGAMES0.98
    13. AI ENGINEER EUROPE1.00
    14. APRIL 10, 20260.97
    15. AlEngineer0.98
    16. BUILDING PI IN A WORLD OF SLOP0.99
    17. EUROPE1.00
    18. PRESENTED BY1.00
    19. Google DeepMind1.00
    20. MARIO ZECHNER / Creator0.97
    21. F0.73
  • 1:41 #15 done53 line(s)

    shot 15·sharpness 1689.0

    1. 12:020.92
    2. EUROPE1.00
    3. Terminal0.97
    4. Local1.00
    5. EARENDIL0.99
    6. /Users/patrikkelemen/WebstormProjects/Asora/src/Agreau/ClientApps/projects/argeau-common/src/lib/shared/uni-table-new/vi0.99
    7. ews-control-panel/vieas-control-panel.component.ts0.97
    8. /Users/patrikkelemen/WebstoraProjects/Asora/src/Agreau/ClientApps/projects/argeau-common/src/lib/shared/uni-table/uni-ta0.99
    9. ble.component.ts1.00
    10. /Users/patrikkelemen/WebstoraProjects/Asora/src/Agreau/ClientApps/projects/argeau-common/src/lib/shared/uni-table-new/cr0.99
    11. eate-view-dialog/create-view-dialog.component.ts0.99
    12. Goo1.00
    13. nd0.99
    14. AIE1.00
    15. /Users/patrikkelemen/WebstormProjects/Asora/src/Agreau/ClientApps/projects/argeau-common/src/lib/shared/uni-table-new/se0.99
    16. rvices/excel-view.service.ts1.00
    17. /Users/patrikkelemen/webstormProjects/Asora/src/Agreau/ClientApps/projects/argeau-commom/src/lib/shared/uni-table-new/se0.98
    18. rvices/views-uni-table.service.ts0.99
    19. /Users/patrikkelemen/webstormProjects/Asora/src/Agreau/ClientApps/projects/argeau-commom/src/lib/shared/uni-table-new/un0.99
    20. i-table-new.component.ts0.99
    21. /Users/patrikkelemen/webstormProjects/Asora/src/Agreau/ClientApps/projects/ergeau-common/src/lib/shared/uni-table/umi-co0.98
    22. lumn.ts0.87
    23. exhorthy0.93
    24. • Search(pattern: "**/«uni-table.ts")0.90
    25. S0.88
    26. AIE1.00
    27. L. Found 11 files0.91
    28. /users/patrikkelemen/webstoraProjects/Asora/src/Agreau/ClientApps/projects/argeau-common/src/lib/shared/uni-tabte/uni-ta0.97
    29. ble-custom-action.ts1.00
    30. /Users/patrikkelemen/WebstoraProjects/Asora/src/Agreau/ClientApps/projects/argeau-common/src/Lin/shared/uni-table/uni-ta0.98
    31. ble.ts0.99
    32. /Users/patrikkelemen/webstoraProjects/Asora/src/Agreau/ClientApps/projects/argeau-common/src/tib/shared/uni-tabte-new/on0.98
    33. All0.78
    34. i-table-views-resolver/uni-table-views.resolver.ts0.99
    35. /Users/patrikkelemen/WebstormProjects/Asora/src/Agreau/ClientApps/projects/argeau-commom/src/lib/shared/uni-table-new/un0.99
    36. i-table-actions-renderer.component.ts0.99
    37. 41.00
    38. /Users/patrikkelemen/webstoraProjects/Asora/src/Agreau/CliemtApps/projects/argeau-commom/src/lib/shared/uni-table-new/un0.98
    39. i-table-template-renderer.component.ts0.99
    40. /Users/patrikkelemen/WebstoraProjects/Asora/src/Agreau/ClientApps/projects/argeau-common/src/lib/shared/uni-table-new/se0.99
    41. rvices/actions-uni-table.service.ts1.00
    42. 18:380.98
    43. 2 spaces0.99
    44. MARIO ZECHNER1.00
    45. @BADLOGICGAMES0.97
    46. AI ENGINEER EUROPE1.00
    47. APRIL 10, 20261.00
    48. AlEngineer0.99
    49. BUILDING PI IN A WORLD OF SLOP0.99
    50. EUROPE1.00
    51. PRESENTED BY1.00
    52. Google DeepMind1.00
    53. MARIO ZECHNER/Creator0.99
  • 1:43 #16 done38 line(s)

    shot 16·sharpness 4457.2

    1. 12:930.94
    2. EUROPE1.00
    3. EARENDIL0.99
    4. Thariq1.00
    5. @trq2121.00
    6. Most people's mental model of Claude Code is that "it's just a TUI" but it0.99
    7. ineer0.97
    8. DeepMind1.00
    9. should really be closer to "a small game engine".1.00
    10. For each frame our pipeline constructs a scene graph with React then0.99
    11. rosof1.00
    12. ineer0.98
    13. -> layouts elements0.99
    14. PE1.00
    15. -> rasterizes them to a 2d screen0.99
    16. -> diffs that against the previous screen1.00
    17. ineer1.00
    18. orkOS0.92
    19. -> finally uses the diff to generate ANSI sequences to draw0.98
    20. We have a ~16ms frame budget so we have roughly ~5ms to go from the1.00
    21. scale1.00
    22. ineer1.00
    23. React scene graph to ANSI written.0.98
    24. 8:04 PM · Jan 21, 2026 ·1.2M Views0.93
    25. 2001.00
    26. 2951.00
    27. 1K1.00
    28. 8761.00
    29. 0.69
    30. MARIO ZECHNER1.00
    31. @BADLOGICGAMES0.95
    32. AI ENGINEER EUROPE APRIL 10, 20261.00
    33. AlEngineer0.98
    34. BUILDING PI IN A WORLD OF SLOP0.98
    35. EUROPE1.00
    36. PRESENTED BY1.00
    37. Google DeepMind1.00
    38. MARIO ZECHNER / Creator0.98
  • 1:45 #17 done43 line(s)

    shot 17·sharpness 4207.7

    1. 12:960.94
    2. EUROPE1.00
    3. EARENDIL1.00
    4. Jessie Frazelle0.97
    5. z00@jessfraz · Jan 230.94
    6. i thought this tweet was a nightmare i had but turns out its real0.99
    7. Thariq1.00
    8. @trq212 · Jan 210.94
    9. eepMind1.00
    10. Replying to @trq2121.00
    11. Most people's mental model of Claude Code is that "it's just a TUI" but it1.00
    12. should really be closer to "a small game engine".0.99
    13. sof0.94
    14. leer0.90
    15. For each frame our pipeline constructs a scene graph with React then...0.99
    16. Show more1.00
    17. orkOS0.98
    18. 111.00
    19. t110.95
    20. 5731.00
    21. 76K0.88
    22. 0.80
    23. Mitchell Hashimoto@mitchellh·Jan240.99
    24. ale1.00
    25. A1.00
    26. neer1.00
    27. I don't appreciate that a follow up tweet gaslit terminals as the problem,1.00
    28. when terminals like Kitty and Ghostty can render every cell changing colors1.00
    29. at around 300fps minimum full screen. And that's being generous, it's0.99
    30. closer to 500+1.00
    31. 101.00
    32. t140.93
    33. 7420.93
    34. h 44K0.76
    35. MARIO ZECHNER1.00
    36. BADLOGICGAMES1.00
    37. AI ENGINEER EUROPE APRIL 10, 20260.96
    38. AlEngineer0.98
    39. BUILDING PI IN A WORLD OF SLOP0.98
    40. EUROPE1.00
    41. PRESENTED BY1.00
    42. Google DeepMind1.00
    43. MARIO ZECHNER/ Creator0.98
  • 1:49 #18 done31 line(s)

    shot 18·sharpness 2639.8

    1. 12:100.98
    2. EUROPE1.00
    3. EARENDIL0.98
    4. Erik Meijer0.99
    5. @headinthebox1.00
    6. er1.00
    7. DeepMind1.00
    8. Flickering in Claude Code seems much improved, but now it has weird0.99
    9. rendering errors.0.99
    10. soft0.95
    11. ineer1.00
    12. C0.96
    13. p0.99
    14. ts on (shift+tab to cycle)1.00
    15. OPE0.82
    16. *0.96
    17. Transmuting.…. (ctrl+c to interrupt · thought for 7s)0.96
    18. er1.00
    19. orkOS0.98
    20. cale0.98
    21. ineer1.00
    22. accept edits on (shift+tab to cycle)1.00
    23. 10:14 PM· Jan 21,2026·38.3K Views0.94
    24. MARIO ZECHNER · BBADLOGICGAMES0.94
    25. AI ENGINEER EUROPE APRIL 10, 20260.99
    26. AlEngineer0.97
    27. BUILDING PI IN A WORLD OF SLOP0.98
    28. EUROPE1.00
    29. PRESENTED BY1.00
    30. Google DeepMind1.00
    31. MARIO ZECHNER/ Creator0.98
  • 1:55 #19 done96 line(s)

    shot 19·sharpness 2465.0

    1. EUROPE1.00
    2. Your context is not your context1.00
    3. 12:161.00
    4. EARENDIL1.00
    5. cchistory1.00
    6. Track Claude Code prompts over time0.99
    7. 1.0.01.00
    8. 1.0.1111.00
    9. By Mario0.99
    10. a Claude Code Version 1.0.00.95
    11. Claude Code Verszon 1.0.330.83
    12. Go1.00
    13. ind1.00
    14. # User Message0.98
    15. Release Date: 2025-05-220.97
    16. Release Date: 2025-09-100.95
    17. # User Message0.89
    18. As you answer the user's questions, you can use the folloving contest:0.94
    19. As you answer the user's questiens, you can use the following context:0.95
    20. NEvER create fies unless they're asolutely necessary for acheving your goal.0.85
    21. ALMYs prefer editing an existing file to creating a new one.0.92
    22. Do what has been asked; nothing more, nothing less.0.97
    23. NEVER proactively create documentation files (w.md) or README files. Only create documentation files if0.92
    24. Do what has been asked; nothing more, nothing less.0.86
    25. ALMYs prefer editing an existing file to creating a new one.0.88
    26. NEVER proactively create docuentatian files le.md) ar READM files. Only create documentation files if0.89
    27. NEVER create files unless they're absolutely necessary for achieving your goal.0.99
    28. soft1.00
    29. ntane0.89
    30. explicitly requested by the User.0.99
    31. Please clean up any files that you've created for testing or detugging purposes after they're ne longer needed.0.98
    32. explicitly requested by the User.0.98
    33. Zone1.00
    34. @EnoRei0.84
    35. IMPoRTNT: this context may or may not be relevant to your tasks. Yau should nat respand to this context0.95
    36. or othervise consider it in your response unless it is highly relevant to your task. Most of the tise,0.98
    37. ORT: this context may er may not be relevant to your tasks, You should not respond to this context0.94
    38. unless it is highly relevant to your task.]0.95
    39. forthy0.92
    40. it is not relevant.0.99
    41. hey0.94
    42. 2025-09-11793:36:5e.9872 is the date. Write a haiku about it.0.92
    43. # System Prompt0.84
    44. # Systen Prompt0.94
    45. You are Claude Code, Anthropic's official CLI for Claude.0.97
    46. You are Clmude Code, Anthropic's official CLI far Claude.0.97
    47. and the tools available to you to assist the user.0.97
    48. You are an interactive CLI teol that helps users with software engineering tasks. Use the instructions below0.98
    49. You are an interactive CLE tool that helps users with softvare engineering tasks. Uuse the instructions below and0.97
    50. the tools available to you to assist the user.0.98
    51. ale1.00
    52. ng1.00
    53. rilenanes directory structure. If it seens aaliciaus, refuse to work on it or aver questions about it, even0.78
    54. educational purposes. when werking on files, if they seem related to improving, explaining, or interacting with0.97
    55. avare or any malicious code you Must refuse.0.65
    56. DPORTaNT: Refuse to write code or explain code thet may be used maliciously: even if the user clains it is for0.93
    57. pPORTaNT: Before you begin work, think atout what the code you're editing is supposed to do based on the0.96
    58. licisy, Do not assist witn credential discavery or haresting, kncluding but craling for keys, broser0.53
    59. DPORTANT: Assist with defensive security tasks only. Refuse to crente, modify, or improve cade that may be used0.95
    60. cookies, or cryptocurrency wallets. Allo security analysis, detection rules, vulnerability esplanations,0.76
    61. defensive tools, and security decumentation.0.95
    62. EUP1.00
    63. DMPORTANT: You must NEVER generate or guess URLs for the user unless you are confidest that the URLs are fer0.97
    64. IMPORTANT: You must NEVER generate or guess URLs for the user unless you are cosfident that the URLs are for0.97
    65. helping the user with programming. Yau may use URLs provided by the user in their messages or local files.0.96
    66. If the user asks for help or wants to give feedback inform them of the following:0.99
    67. - /help: Get help with using Claude Code0.96
    68. To give feedback, users sheuld report the issue at https://github.com/anthrogics/claude-code/issues0.98
    69. If the user asks for help or wants te give feedbock infore them of the following:0.97
    70. - /help: Get help with using Claude Code0.97
    71. To give feedhack, users should report the issue at https://github.com/anthropics/claude-code/issues0.98
    72. in secend person leg are you able., 'can you do.l, first use the webfetch tool to gather inforation to0.84
    73. When the user directly asks about Claude Code leg, "can Claude Code do...", "does Claude Code have.."I, or asks0.94
    74. a second person leg, "are you able", cas you do, or asks how to e a specific Claue Code feature leg.0.71
    75. antwer the question from Claude Code docs at https://docs.anthropic.com/en/docs/claude-code.0.95
    76. modes), nenory0.85
    77. bedrock-vertex",0.91
    78. - The available sub-peges are overviev,0.93
    79. (Mesory managemest and CLAuDe.ad), settings, security' (Pernissions and teols), costs,0.82
    80. tutorials (Extended thinking, pasting images, and conon workflows),0.83
    81. (CLI cammands, CLI flags, SOK, slash commands, and0.94
    82. troubleshooting0.94
    83. from Claude Code docs. The list of available docs is available at https://docs.anthropic.com/en/docs/claude0.94
    84. code/claude_code_docs_sap.nd.0.93
    85. Example: httosi//docs.anthropic.com/en/docs/claude-code/cli-usage0.95
    86. MARIO ZECHNER1.00
    87. @BADLOGICGAMES0.99
    88. AI ENGINEER EUROPE0.99
    89. APRIL 10, 20261.00
    90. AlEngineer0.98
    91. BUILDING PI IN A WORLD OF SLOP0.99
    92. EUROPE1.00
    93. PRESENTED BY1.00
    94. Google DeepMind0.98
    95. MARIO ZECHNER / Creator0.97
    96. F0.93
  • 2:02 #20 done97 line(s)

    shot 20·sharpness 2500.1

    1. Your context is not your context1.00
    2. 12:231.00
    3. EARENDIL1.00
    4. cchistory1.00
    5. Track Claude Code prompts over time0.99
    6. 1.0.00.99
    7. 1.0.1110.99
    8. By Mario0.95
    9. # Claude Code version 1.0.00.92
    10. # Claude Code Version 1.0.2130.88
    11. Release Date: 2025-05-220.99
    12. Release Date: 2825-09-100.95
    13. # User Message0.95
    14. # User Message0.90
    15. Snor1.00
    16. As you answer the user's questsons, you can wse the folloving contest:0.92
    17. ALMYs prefer editing an existing file to creating a new one.0.94
    18. Do what has been asked; nothing more, nothing less.0.97
    19. NEVER create files unless they're absolutely necessary for achieving your goal.0.99
    20. NEVER proactively create documentation files (e.md) or README files. Only create documentation files if0.92
    21. rtant-instruction0.97
    22. -reminders0.97
    23. As you answer the user's questiens, you can use the folloving cantest:0.92
    24. Do what has bee asked; nothing more, nothing less.0.97
    25. ALAYs prefer editing an existing file to creating a new one.0.90
    26. NEVER proactively create docuentatian files le.nd) ar REAM files, Only create documentation files if0.89
    27. NEVER create files unless they're absolutely necessary for achieving your poal.0.98
    28. <systen0.88
    29. rtant-instruction-0.96
    30. explicitly requested by the User.1.00
    31. Please clean up any files that you've created for testing or debugging purposes after they're ne longer needed.0.98
    32. explicitly requested by the User.0.98
    33. IMPoRTT: this context may or may not be relevant to your tasks. You should net respond to this contest0.95
    34. or otherwise consider it in your response unless it is highly relevant to your task. Most of the time,0.98
    35. unless it is highly relevant to your task.]0.96
    36. IMPoRTaT: this cantext may er may mot be relevant te your tasks. You should not respond to this context0.95
    37. it is not relevant.0.97
    38. Engine0.98
    39. 2825-09-11703:36:50.9872 is the date., Write a haiku about it.0.92
    40. EUROPE0.97
    41. ILon0.58
    42. # Systen Prospt0.92
    43. # Systen Prospt0.96
    44. Duphb0.79
    45. You are Claude Code, Anthropic's official C.I for Claude.0.97
    46. You are Claude Code, Anthropic's official CLI for Claude.0.97
    47. Zone0.99
    48. and the tools available to yeu to assist the user.0.98
    49. You are an interactive CLI teol that helps users with software engineering tasks. Use the instructions below0.98
    50. You are an interactive CLI tool that helps users with softvare engineering tasks. Use the instructions below and0.98
    51. the tools available to you to assist the user.0.97
    52. Microst0.94
    53. educational purposes. when werking on files, if they seem related to isproving, explaining, or interacting with0.96
    54. filenanes directory structure If it sees mlicious, refuse to work on it or asver questions about it, even0.73
    55. avare or any malicious code you MST refuse.0.70
    56. DPORTaNT: Refuse to write code or explain code that may be used malicinusly: even if the user clains it is for0.94
    57. pPORTaNT: Before you begin work, think about what the code you're editing is supposed to do based on the0.96
    58. licisy, Do nt assist wit credetial discvery or harvesting, ncluding but craling for s key, brser0.52
    59. defensive tools, and security decumentation.0.92
    60. DMPORTANT: Assist with defensive security tasks only. Refuse to crente, modity, or improve cade that may be used0.93
    61. cookies, or cryptocurrency wallets. Allow security analysis, detectian rules, vulnerability explanations,0.93
    62. IMPORTANT: You must NEVER generate or guess URLs for the user unless you are confsdest that the URLs are fer0.97
    63. IMPORTANT: You must NEVER penerate or guess UR.s for the user unless you are confident that the URLs are for0.98
    64. helping the user with programning. Yau may use URLs provided by the user in their sessages or local files.0.96
    65. If the user asks for help or wants to give feedback infore then of the following:0.98
    66. - /help: Get help with using Claude Code0.96
    67. Te give feedback, users sheuld report the issue at https://github.com/anthregics/claude-code/issues0.98
    68. If the user asks for help or wants to give feedback infore then of the following:0.97
    69. - /help: Get help with using Claude Code0.96
    70. To give feedhack, users should repart the issue at https://github.com/anthropics/claude-code/issues0.97
    71. NEngi0.91
    72. jineer0.91
    73. in second person leg are you able.., can you do.., first use the webfetch tool to gather Inforation to0.83
    74. ansver the question from Claude Code docs at https://docs.anthrspic.com/en/docs/claude-code.0.89
    75. modes), enory0.83
    76. bedrock-vertex,0.89
    77. - The available sub-peges are overview,0.92
    78. (Menory managenent and CLADe.ad), 'settings', security' (Pernissions and tools), costs,0.86
    79. tutorials (Extended thinking, pasting images, and canon workflows),0.79
    80. (CLI commands, CLI flags, SOK, slash commands, and0.94
    81. troubleshoat ing0.90
    82. When the user directly asks sbout Claude Code leg, "can Claude Code do...", "does Claude Code have..."), or asks0.94
    83. a second persn leg, "are you abl.", ca you do, or asks how to use a specific Claude Code feature leg.0.71
    84. fre Claude Code docs, The list of avalable docs is available at htpsi//óocsanthropic c/en/docs/claude0.74
    85. cade/claude_code_docs_map.ed.0.92
    86. Example: httos://docs.anthropic.com/en/docs/claude-code/cli-usage0.96
    87. MARIO ZECHNER1.00
    88. @BADLOGICGAMES0.97
    89. AI ENGINEER EUROPE1.00
    90. APRIL 10, 20261.00
    91. BUILDING PI IN A WORLD OF SLOP1.00
    92. AlEngineer0.97
    93. EUROPE1.00
    94. PRESENTED BY1.00
    95. Google DeepMind1.00
    96. MARIO ZECHNER / Creator0.97
    97. F0.86
  • 2:24 #21 done4 line(s)

    shot 21·sharpness 2530.8

    1. 12:451.00
    2. Your context is not1.00
    3. your context1.00
    4. EARENDIL1.00
  • 2:35 #22 done

    shot 22·sharpness 308.4

  • 2:37 #23 done

    shot 23·sharpness 1298.9

The page's on-screen-text budget of 600 lines is spent, so the last cards in this grid list fewer lines than they hold. Narrow the page with ?frames= to read them.

Transcript

279 cues· 3,340 words· 18,059 chars

  1. 0:15 I'm Mario, I built Pi in a world of slop, and this is a tragedy in three acts.
  2. 0:21 Just to talk about this real quick, a bunch of people on the internet gave me money for ad space on my torso, and all of that goes to a charity, so yeah, thanks guys.
  3. 0:29 So, act one, building Pi.
  4. 0:31 In the beginning, there was cloud code, and it was good, right?
  5. 0:34 We all got basically catnipped by that thing and stopped sleeping.
  6. 0:39 A bunch of stuff before that, but Cloud Code was the one thing that kind of clicked with me the most.
  7. 0:45 And to preface all of this, I love the Cloud team.
  8. 0:48 They're brilliant people, talented, super high velocity.
  9. 0:51 So they also created the entire game.
  10. 0:55 Major props to them.
  11. 0:55 So this is not a roast.
  12. 0:56 This is just me, an old man, telling you why I stopped using Cloud Code and built my own thing.
  13. 1:02 In 2025, I started using Cloud Code in about April, I think, thanks to Peter, because he told us the agents are working now.
  14. 1:12 Back then, it was simple and predictable and fit my workflow, but eventually,
  15. 1:17 The token madness got hold of them, I think, and the team got bigger, and they started dogfooding that stuff and built a lot of features, a lot of features I don't need, which is fine.
  16. 1:26 I can just ignore them.
  17. 1:27 But with velocity and more features come more bugs, and that's bad because I used to work at construction sites, and if my hammer breaks every day, I'm getting really mad.
  18. 1:36 And if my development tools break every day, I'm also getting mad.
  19. 1:40 So there was this.
  20. 1:41 It's just a running gag.
  21. 1:42 And here's Tarik telling us that Cloud Code is now a game engine.
  22. 1:45 And here's Mitchell from Ghosty telling us, no, it's not.
  23. 1:48 And eventually, they fixed the flicker, but then other stuff broke.
  24. 1:51 And I think they're now in the third iteration of a 2E renderer.
  25. 1:55 Yeah.
  26. 1:55 But that's just a symptom.
  27. 1:57 The real problem is that my context wasn't my context.
  28. 2:00 Cloud Code is the thing that controls my context.
  29. 2:03 And behind my back, Cloud Code does things.
  30. 2:06 to the context.
  31. 2:07 So you have the system prompt, which changes on every release, including the tool definitions.
  32. 2:11 They would remove tools, modify tools.
  33. 2:14 It's not good.
  34. 2:15 They would insert system reminders in the most inopportune place in your context, telling the model, here's some information.
  35. 2:22 It may or may not be relevant to what you're doing.
  36. 2:25 That it actually says it may or may not be relevant what you're doing.
  37. 2:29 And that kind of confused the model, and that kind of broke my workflows.
  38. 2:34 On top of all that, there's zero observability, because that's how the tool is constructed, and I like knowing what my agents are doing.
  39. 2:40 There's zero model choice, which is obvious.
  40. 2:42 It's the native entropic harness, so it makes sense for them to want you to use clouds, right?
  41. 2:47 And there's almost zero extensibility, and some of you might have written some hooks for Cloud Code, but I'm telling you the number of hooks and the depth of those hooks is very shallow, and every time a hook triggers, what actually happens is a new process gets spawned, basically the command you specified for the hook to be executed, and I don't find that specifically efficient.
  42. 3:06 So I took a step back and looked around for alternatives, and I'd like to especially call out AMP and FactoryDroid, the Porsche and Lamborghini of coding agent harnesses.
  43. 3:16 So if you can afford them, please use them.
  44. 3:18 They're at the frontier.
  45. 3:19 They're really good, and the teams are fantastic.
  46. 3:21 And there's a bunch of other options.
  47. 3:22 And I have history in OSS, so naturally I kind of gravitated towards open code.
  48. 3:27 And again, brilliant team, super high execution velocity, and they don't sell you hype.
  49. 3:33 They sell you tools that work for the most part.
  50. 3:36 I started looking under the hood of open code with respect to context handling as well, because that's the most important part for me.

Chapters

  1. 0:00 Intro and motivation for building pi
  2. 0:29 Act 1: Building pi and the frustration with existing agent harnesses
  3. 1:56 Why current context management in tools like Cloud Code and Open Code fails
  4. 4:44 The importance of minimal harnesses and the "Terminal" benchmark
  5. 5:35 Introducing pi: A self-modifying, extensible agent core
  6. 7:27 The "YOLO" security philosophy and extensibility through TypeScript
  7. 9:03 Examples of pi extensions (chat rooms, NES, Doom)
  8. 10:46 Act 2: OSS in the age of "clankers" and how to fight them
  9. 12:03 Act 3: A plea to slow down and stop the "slop" in software development
  10. 13:58 How agents create "enterprise-grade complexity" and why humans are still the bottleneck
  11. 16:12 Practical advice: How to effectively integrate agents into your workflow

Open at this second