Videos jVjt-2g8NMY
A Genius With Amnesia - Victor Savkin, Nx
Scene timeline
91 shot(s).
keyframes kept every frame deduplicated
What was stored
- cues
- 267
- whisperx 267
- chunks
- 36
- from 267 cues
- keyframes
- 76
- kept of 91 captured
- frames with text
- 76
- 2,127 lines read
- chapters
- 0
- from the source metadata
- keyframe bytes
- 10.9 MB
- word timings on 267 cues
Provenance
| stage | state | model | started | took |
|---|---|---|---|---|
fetch |
done | — | 2026-08-11 08:31 | 1m 15s |
stt |
done | — | 2026-08-11 08:32 | 20s |
chunk |
done | — | 2026-08-11 08:33 | 0s |
text_embed |
done | — | 2026-08-11 08:33 | 1s |
keyframe |
done | — | 2026-08-11 08:33 | 2m 27s |
ocr |
done | — | 2026-08-11 08:35 | 1m 16s |
frame_embed |
done | — | 2026-08-11 08:37 | 12s |
Frames, and what the machine read
-
- AI Engineer World's Fair 20260.98
- Genius with Amnesia0.98
- June 20260.98
- Victor Savkin0.99
- ←Previous1.00
- Next→0.99
-
- Promise1.00
- The Valley1.00
- How can1.00
- ANTIQUES & ODDITIES0.99
- I help?0.94
- Monorepos1.00
- forever1.00
- OPEN1.00
- Monorepos1.00
- forever1.00
- I need a0.98
- As you1.00
- Let's start1.00
- genius to1.00
- Cranking1.00
- help with0.96
- wish.1.00
- my impossible1.00
- project.1.00
- Monorepos1.00
- forever1.00
- ← Previous0.97
-
- Reality1.00
- No, we have0.98
- I can't0.98
- I already1.00
- a standard way1.00
- of doing it!1.00
- see it1.00
- explained it0.97
- to you!1.00
- Monorepos1.00
- Monorepos1.00
- forever1.00
- Sorever0.85
- STANDARD1.00
- FLOW1.00
- <1>0.86
- EVERY TIME0.99
- git push1.00
- <1>0.87
- pray1.00
- You just did1.00
- I have no1.00
- You are1.00
- it in the1.00
- memory of1.00
- absolutely1.00
- other repo0.99
- that1.00
- right!1.00
- Monorepos1.00
- forever1.00
- </>0.86
- OTHER REPO0.98
- THIS REPO1.00
- ·BUILD0.94
- git push1.00
- -BUILD0.98
- ·TEST0.95
- ·TEST0.90
- ·LINT0.86
- -DEPLOY0.99
- MATTERS1.00
- CONSISTENCY1.00
- <1>0.87
- -DEPLOY0.92
- ← Previous0.96
-
- 02 · HOW DO WE SOLVE IT0.97
- EXAMPLE1.00
- Count Unnecessary Reexplaining0.98
- 011.00
- Explain the UI change0.99
- Platform0.95
- Reexplain the published UI0.99
- uses modules1.00
- change while integrating it into1.00
- Module 10.98
- Explain the Module 1 issue0.96
- before publishing the updated1.00
- UI change0.96
- Module 10.99
- awaiting UI change1.00
- Module 21.00
- awaiting fixed UI0.98
- Reexplain the fixed UI change0.99
- while integrating it into Module1.00
- Reexplain the fixed UI change0.99
- while integrating it into Module1.00
- 21.00
- UI0.99
- Explain everything while1.00
- integrating into Platform1.00
- UI change explained1.00
- One weel1.00
- change to1.00
- UNNECESSARY REEXPLAINING1.00
- ↑↓ or n/p to step (1/7)0.99
- ← Previous0.97
-
- 02 · HOW DO WE SOLVE IT0.97
- EXAMPLE1.00
- Count Unnecessary Reexplaining0.98
- Explain the UI change0.99
- Platform1.00
- Reexplain the published UI0.99
- uses modules1.00
- Module 10.99
- change while integrating it into1.00
- Explain the Module 1issue0.98
- before publishing the updated1.00
- UI change0.93
- Module 10.95
- issue explained1.00
- Module 21.00
- awaiting fixed UI0.98
- Reexplain the fixed UI change1.00
- while integrating it into Module1.00
- Reexplain the fixed UI change0.99
- while integrating it into Module1.00
- 21.00
- UI0.99
- Explain everything while1.00
- integrating into Platform1.00
- published UI change1.00
- One weel1.00
- change tc0.94
- UNNECESSARY REEXPLAINING1.00
- ↑↓ or n/p to step (3/7)0.99
- ← Previous0.98
-
- 02 · HOW DO WE SOLVE IT0.97
- EXAMPLE1.00
- Count Unnecessary Reexplaining0.98
- Explain the UI change0.98
- Platform1.00
- Reexplain the published UI0.99
- integration explained1.00
- Module 11.00
- change while integrating it into1.00
- Explain the Module 1 issue0.97
- before publishing the updated1.00
- UI change0.94
- Module 10.96
- Module 21.00
- Reexplain the fixed UI change0.99
- while integrating it into Module1.00
- fixed change integrated0.99
- fixed change integrated1.00
- Reexplain the fixed UI change0.99
- while integrating it into Module1.00
- 21.00
- fixed UI change1.00
- UI1.00
- 060.99
- Explain everything while0.99
- integrating into Platform0.98
- One weel1.00
- change tc0.97
- UNNECESSARY REEXPLAINING1.00
- ↑↓ or n/p to step (6/7)0.98
- ← Previous0.96
-
- PART1.00
- How do we solve it1.00
- ← Previous0.97
-
- 02 . HOW DO WE SOLVE IT0.97
- PROBLEMS TO SOLVE1.00
- There are many. They fall into1.00
- two categories.1.00
- 021.00
- Repo boundaries1.00
- Amnesia1.00
- The agent can only see and change one repo at a0.99
- The agent forgets the work as a whole, every1.00
- time, never the system around it.1.00
- session starts from scratch.1.00
- ↑↓ or n/p to step (2/2)0.99
- ← Previous0.98
-
- 02 · HOW DO WE SOLVE IT0.97
- REPO BOUNDARIES· READS0.98
- Reads stop at the repo edge.0.99
- With no model of the whole org, the agent leans on a human to do the research.1.00
- repoedge1.00
- API0.99
- Can't align code with the rest of the system1.00
- Al agent0.96
- Design System1.00
- your repo0.95
- Can't infer best practices and standards0.99
- Mobile App0.99
- ↑↓ or n/p to step (2/2)0.99
- ← Previous0.95
-
- 02 · HOW DO WE SOLVE IT0.97
- REPO BOUNDARIES· WRITES0.98
- Writes stop at the repo edge.0.99
- It can't change all the relevant code across repos, so a human coordinates it.1.00
- repo edge0.95
- APl consumer0.95
- Can't validate downstream1.00
- Al agent0.94
- Mobile App1.00
- Can't update consumers1.00
- edits one repo1.00
- Can't refactor everywhere0.99
- Service B0.99
- ↑↓ or n/p to step (3/3)0.98
- ←Previous1.00
-
- 02 · HOW DO WE SOLVE IT0.97
- PROBLEMS TO SOLVE1.00
- The second category: the agent forgets.0.99
- The agent has no episodic memory. Every session starts1.00
- from a blank slate, so the human becomes the memory.1.00
- ← Previous0.96
-
- 02 · HOW DO WE SOLVE IT0.96
- Together, they form one graph of the work done.1.00
- Session A1.00
- auth refactor1.00
- Session C0.97
- API v20.97
- Session graph0.98
- Session B0.98
- add SSO1.00
- All the conversations and1.00
- decisions about the work.1.00
- sdk1.00
- Repo graph0.98
- repo 51.00
- Hard code artifacts produced by0.99
- your org.0.97
- api-core1.00
- auth-lib1.00
- repo 41.00
- repo 11.00
- gateway1.00
- repo 31.00
- tokens1.00
- repo 20.99
- session follows session1.00
- repo depends on repo1.00
- This is what the agent should see.1.00
- ← Previous0.95
-
- 02· HOW DO WE SOLVE IT0.98
- This is what agent sees1.00
- Session graph0.97
- All the conversations and1.00
- decisions about the work.0.98
- Repo graph0.94
- Hard code artifacts produced by0.99
- your org.1.00
- auth-lib1.00
- repo11.00
- session follows session1.00
- repo depends on repo0.98
- So it leans on the one who actually understands what is going on: the0.99
- developer.1.00
- ← Previous0.96
-
- 02· HOW DO WE SOLVE IT0.98
- This is what agent sees1.00
- Session graph0.97
- All the conversations and1.00
- decisions about the work.0.98
- Repo graph0.94
- Hard code artifacts produced by0.99
- your org.1.00
- auth-lib1.00
- repo11.00
- session follows session1.00
- repo depends on repo0.98
- So it leans on the one who actually understands what is going on: the0.99
- developer.1.00
- ← Previous0.96
-
- 03 . HOW WE SOLVE IT0.94
- An1.00
- ta-Harness1.00
- * Polygraph0.95
- ← Previous0.98
-
- 03 . HOW WE SOLVE IT0.96
- THE IDEA0.98
- The synthetic0.96
- monorepo1.00
- Connect separate repositories into one1.00
- unified dependency graph, without1.00
- Mobile App1.00
- Design System1.00
- moving a single line of code.0.99
- SEPARATE1.00
- SYNTHETIC1.00
- ↑↓ or n/p to step (1/1)0.99
- ← Previous0.97
-
- 03 . HOW WE SOLVE IT0.95
- HO0.63
- ← Previous0.97
-
- 03. HOW WE SOLVE IT0.96
- prettier/prettier1.00
- oss0.99
- OSS repository - 0 projects0.97
- 1100.91
- 519011.00
- DEPENDS1.00
- USED BY1.00
- STARS1.00
- Prettier is an opinionated code formatter.0.99
- Owner: prettier Branch: main1.00
- Indexed Jun 4 Metadata Jun 40.99
- ← Previous0.96
-
- 03. HOW WE SOLVE IT0.96
- O0.52
- prettier/prettier1.00
- oss0.99
- OSS repository- 0 projects0.96
- 00.99
- 1101.00
- 519011.00
- DEPENDS0.99
- USED BY0.99
- STARS1.00
- Prettier is an opinionated code formatter.0.99
- Owner: prettler Branch: main0.99
- Indexed Jun 4 Metadata Jun 40.99
- ← Previous0.98
-
- chalk/chalk1.00
- ng_module_issue_repro1.00
- 03· HOW WE SOLVE IT0.95
- ivyplay1.00
- mgechev/codelyzelazyload_angular13 ng1ng2router0.99
- postcss/postcss-url1.00
- samplenxmoderntools1.00
- ckackngrx/platform0.99
- extra1.00
- patched_cli1.00
- Package package0.98
- package0.97
- weback-kartial-build0.57
- angular-cli1.00
- ivostok1.00
- angular-consoleular/angular,x/rxjs0.97
- kage1.00
- package0.77
- nackage0.99
- webpack/stylus-loader1.00
- package1.00
- package1.00
- 业0.92
- ss.js0.94
- package1.00
- testwarning2zy-loading-c1 nwa-bigbank-example0.99
- P0.74
- postcss/autoprefixer1.00
- routerrefresh1.00
- nx-dev-ergonomics1.00
- package1.00
- testwarning0.99
- ngular1.00
- nx-large-repo-perf1.00
- ianschmitz/jest-environment-jsdom-fourteen1.00
- nmfr/optimize-css-assets-webpack-plugin1.00
- trypercy1.00
- redwood1.00
- r-eslint1.00
- clouddte1.00
- cypress-iocypftitypescrintonnect0.71
- tryactions1.00
- webshowactionszcument-registerelementd0.94
- nx-azure-build-11.00
- jestjs/jest1.00
- createtestconnect1.00
- jenkins-setup1.00
- test-nx-cloud1.00
- myangulartest1.00
- design-systen1.00
- testd11.00
- happyorgtest1.00
- nx-shops-circle1.00
- empty-workspace1.00
- demo41.00
- nappyorgtestmon0.98
- demoapp1.00
- testgithub1.00
- prettier/prettier1.00
- ← Previous0.96
-
- 03 . HOW WE SOLVE IT0.94
- ← Previous0.96
-
- 03 - HOW WE SOLVE IT0.95
- 业0.93
- ← Previous0.99
-
- 03 - HOW WE SOLVE IT0.95
- ← Previous0.97
Transcript
267 cues· 3,213 words· 17,100 chars
- 0:04 Imagine you find a magic lamp in an antique store.
- 0:07 You rob it, a genie appears and asks how it can help.
- 0:12 You bury it in the end line so you say I need the best engineer to help with an impossible project at work.
- 0:18 And the genie grants your wish.
- 0:20 For me the best engineer is probably John Carmack from his Eid days, so you get Carmack.
- 0:25 But the genie has a sense of humor and imposes restrictions.
- 0:29 Maybe for safety.
- 0:31 Karmak can only see one small part of your codebase, maybe one thousandth of it.
- 0:36 And he remembers nothing he did before.
- 0:38 Every conversation starts fresh.
- 0:41 That would be maddening, right?
- 0:42 You would know there is a standard way to do stuff and Karmak wouldn't.
- 0:46 You would have to explain the same thing over and over and over again.
- 0:50 You have a genius on one side and something deeply deficient on the other.
- 0:55 And that's what agents are.
- 0:57 Let me walk you through an example of how many times we explain things in a simple interaction.
- 1:03 We have four repos, UI, Module 1, Module 2, and Platform.
- 1:09 I want to change the UI and propagate the change through the system.
- 1:13 First, we change the UI library.
- 1:14 Say we change the button or whatever.
- 1:17 That's the first explanation.
- 1:18 Unavoidable.
- 1:19 We have to express the intent.
- 1:22 Then we publish it.
- 1:23 We go to module one and we have to explain what just has happened in the UI library so it can consume the package here.
- 1:30 Know that that's often a different person.
- 1:32 Every box in this diagram can be done by a different person.
- 1:37 And then we discovered that the published UI library doesn't work with module one.
- 1:43 So we go back to UI and we have to re-explain the original change and the issue, right?
- 1:51 Because as a new agent, it doesn't know the original change and obviously it doesn't know about the issue.
- 1:57 Let's say we fix it, right?
- 1:59 And publish it again.
- 2:01 We go and again, we explain the new change in the context of module one, same ordeal.
- 2:07 I'm going to do the same for module two again.
- 2:10 And then we go to the platform repo and we explain how everything fits together and we implement the change there.
- 2:17 Let's imagine a week after release, a bug appears in the UI component and we have to fix it.
- 2:23 So we start an agent in the UI repo.
- 2:26 And we have to explain, again, the original change from a week ago and this production issue we've seen.
- 2:32 So we have seven explanations for what essentially is one change.
- 2:37 And also it may not be one person making all these seven explanations, but they still occur, right?
- 2:43 So that's very, very typical with agents.
- 2:46 So how do we solve it?
- 2:50 Well, there are many problems in here that contribute to this experience, but they roughly fall into two categories.
- 2:58 The first one is that an agent essentially is repo bound.
- 3:03 The agent sees and changes generally one repo at a time.
- 3:08 It never sees the whole system, which can be hundreds or thousands of repos.
- 3:14 So that's kind of the space component of the problem.
- 3:18 Second is amnesia.
- 3:19 The agents forget their work.
- 3:21 Every session starts with a blank slate.
loading