Videos AMiyLItEtLA
fighting slop with slop — Vaibhav Gupta, Boundary
Scene timeline
103 shot(s).
keyframes kept every frame deduplicated
What was stored
- cues
- 277
- whisperx 277
- chunks
- 39
- from 277 cues
- keyframes
- 85
- kept of 103 captured
- frames with text
- 84
- 4,097 lines read
- chapters
- 13
- from the source metadata
- keyframe bytes
- 15.5 MB
- word timings on 277 cues
Provenance
| stage | state | model | started | took |
|---|---|---|---|---|
fetch |
done | — | 2026-08-09 21:50 | 0s |
stt |
done | — | 2026-08-09 02:57 | 24s |
chunk |
done | — | 2026-08-09 02:57 | 0s |
text_embed |
done | — | 2026-08-10 19:37 | 1s |
keyframe |
done | — | 2026-08-09 02:57 | 3m 32s |
ocr |
done | — | 2026-08-09 03:01 | 58s |
frame_embed |
done | — | 2026-08-10 19:37 | 14s |
Frames, and what the machine read
-
- AlEngineer0.96
- World's Fair0.97
-
- AlEngineer0.95
- World's Fair0.99
-
- LAB & PLATINUM SPONSORS0.97
- Amazon AGI Lab0.99
- ANTHROP\C1.00
- Google DeepMind1.00
- MINIMAX0.98
- OpenAl0.92
- Akamai1.00
- arize1.00
- aws1.00
- Braintrust bright data0.99
- B1.00
- Browserbase1.00
- docker1.00
- :neo4j0.91
- ORACLE1.00
- PayPal1.00
- qodo0.99
- reducto1.00
- Sonar1.00
- Makers of1.00
- together.ai0.98
- Unblocked1.00
- WorkOS1.00
- SonarQube1.00
-
- AlEngineer0.99
- AlEngineer0.99
- WorkOS1.00
- World's Fair1.00
- Amazon AGI Lab1.00
- World's Fair0.98
- World's Fair0.96
- AlEngineer0.99
- Braintrı0.93
- World's Fair0.99
- AIEngineer0.95
- OpenAI0.93
- W0.99
- AlEng'0.87
- AlEngineer0.99
- aws1.00
- Worl0.93
- fight slop with slop0.99
- togetherai1.00
- World's Fair0.98
- AlEngineer1.00
- AlEngineer0.97
- World's Fair1.00
- World's Fair0.99
- DATADOG1.00
- W0.99
- CLOUDFL0.99
- AlEnginee1.00
- AlEngineer1.00
- LanceDB1.00
- World's1.00
- builder.io1.00
- World's Fair0.99
- World's Fair0.96
- AlEngineer1.00
- TOFHA0.74
- World's Fair0.99
- AlEngineer0.99
- cognee1.00
- W0.98
-
- AlEngineer0.98
- World's Fair0.96
- Fight slop with slop1.00
- or1.00
- How we ship serious software1.00
- without ever reading the code1.00
- AlEngineer0.99
- Jst0.90
- World'sFai1.00
- BAML1.00
- ail0.82
- fight slop with slop0.98
- gether1.00
- AlEngineer0.99
- 'd'sFai1.00
-
- AlEngineer0.99
- World's Fair0.98
- No code reviews.1.00
- 010.99
- You must work on things in parallel.1.00
- 020.95
- Use Al however you want.0.98
- 031.00
- AlEnginee0.97
- ntrust1.00
- World's1.00
- PBAML0.93
- neer1.00
- 'sFai0.91
- fight slop with slop0.98
- get1.00
- Enginee0.96
- d's0.94
- LARE1.00
-
- we're probably a1.00
- AlEnginieer0.94
- World's Fair0.98
- zoomer YC startup0.98
- Braintru0.98
- Wc0.99
- BAML1.00
- — AlEngine0.93
- lorld'0.90
- Wc0.98
- LOUDF0.94
-
- AlEngineer0.98
- World's Fair0.99
- WA1.00
- WASHINGTON1.00
- DRIVER LICENSE0.98
- USA1.00
- FEDERAL LIMITS APPLY1.00
- 4d LIC#1.00
- 9CLASS1.00
- DONOR1.00
- 1GUPTA1.00
- clearly millenial0.99
- 2VAIBHAV1.00
- 3 DOB 02/200.97
- /19940.92
- 4a Iss 08/14/20220.94
- 8 1823 MINOR AVE0.99
- 17040.96
- SEATTLE WA 98101-09250.98
- 15 SEX M0.98
- 18 EYES BLK1.00
- 16 HGT 5'-07"1.00
- 17WGT 130 lb0.92
- AlEngineer0.99
- 12 RESTRICTIONS1.00
- 9a END NONE1.00
- trust1.00
- Norld'sF0.98
- B1.00
- 4b EXP 02/20/20270.98
- BAML1.00
- Fai1.00
- fight slop with slop0.97
- geth0.92
- AlEngineer-0.92
- 1d'sF0.95
- ARE1.00
-
- AlEngineer0.99
- World'sFair1.00
- BAML1.00
- AlEngineer0.98
- itrust0.99
- World'sI0.91
- BAML1.00
- Fai1.00
- fight slop with slop0.99
- geth1.00
- Engineering the future of Al0.99
- AlEngineer1.00
- ld'sl0.86
- .ARE0.97
-
- AlEngineer1.00
- World'sFair1.00
- SLOP1.00
- BAML1.00
- AlEngineer0.98
- trust1.00
- World'sF0.99
- BAML1.00
- Fai1.00
- fight slop with slop0.98
- geth0.96
- Engineering the future of Al1.00
- AlEngineer0.98
- rld'sF0.97
- ARE1.00
-
- AlEngineer0.98
- “To know your slop,0.98
- World's Fair0.96
- you must become your slop”0.96
- - Slop Tzu0.99
- AIEngine0.94
- intru:0.97
- World's1.00
- PBAML0.97
- ineer0.89
- 'sFai0.94
- stcslop wit slop0.76
- toget0.94
- Engineering the future of Al0.99
- — AlEngine0.86
- Vorld's1.00
- FLARE1.00
-
- AlEngineer0.98
- World's Fair0.93
- Slop1.00
- pronounced släp1.00
- Any code you don't read0.99
- AlEngin0.94
- intrt0.93
- World'0.99
- PBAML0.89
- gineer1.00
- I's0.99
- fight slop with slop0.97
- toge1.00
- Engineering the future of Al1.00
- AlEngin0.97
- Norld'0.90
- FLARI0.93
-
- No code reviews.1.00
- AlEngineer0.99
- World's Fair0.97
- You must work on things in parallel.1.00
- Hit0.51
- Use Al however you want.1.00
- SLOP1.00
- SLOP1.00
- BAML1.00
- Braintr0.98
- Worl0.96
- PBAML0.95
- AlEngin0.99
- rld'0.92
- fight slop with slop0.98
- to1.00
- Engineering the future of Al1.00
- Worl1.00
- UDFLA1.00
-
- Skirmish of Standards1.00
- AlEngineer0.98
- World's Fair0.94
- casualty: 200M tokens lost1.00
- AlEngine0.99
- intrust0.99
- World's1.00
- PBAML0.86
- jineer -0.87
- I'sF0.91
- fight slop with slop0.97
- toge1.00
- Engineering the future of Al1.00
- Engine1.00
- Vorld's1.00
- FLARE1.00
-
- Situation1.00
- Rule1.00
- AlEngineer0.99
- World'sFair1.00
- Adding a feature0.99
- Put it in the highest (earliest) layer possible1.00
- belong in the AST layer.0.99
- Changing AST0.96
- Relatively forgiving — this is where most wc1.00
- Changing HIR1.00
- Discuss with at least one person who works1.00
- Changing TIR1.00
- Discuss with at least one person who works0.99
- Changing MIR or Emit1.00
- Discuss with at least two people. You are al0.99
- making a mistake unless you have a very sp1.00
- Adding a new layer1.00
- Requires explicit approval from the tech lea1.00
- contributor. No new layers without significa1.00
- AlEngi0.95
- aintru60.85
- World1.00
- Architecture.md1.00
- BAML1.00
- 'nginr0.93
- d'0.97
- fight slop with slop0.99
- toge0.95
- Engineering the future of Al1.00
- AlEngi0.95
- World1.00
- DFLA0.88
-
- Battle of Design1.00
- AlEngirieer0.97
- World's Fair0.97
- casualty: 5B+ tokens1.00
- AlEngine0.97
- intrust0.99
- World's1.00
- PBAML0.87
- jineer –0.90
- 'sF0.95
- fight slop with slop1.00
- toge1.00
- Engineering the future of Al0.99
- AlEngine0.95
- Vorld's0.95
- FLARE1.00
-
- AlEngineer1.00
- World's Fair0.99
- "Code can be slop,0.99
- writing cannot"0.99
- - me (with taste)1.00
- AlEngin0.95
- intrust1.00
- World'0.99
- PBAML0.85
- gineer —0.93
- I'sFi0.90
- fight slop with slop0.97
- oge0.99
- Engineering the future of Al0.99
- - AlEngin0.91
- lorld'0.94
- FLARE1.00
-
- BAML Enhancement Proposals1.00
- hellovai1.00
- AlEngineer0.98
- World's Fair0.97
- All Proposals0.97
- Export All BEPs1.00
- New BEP0.99
- Q Search BEPs...1.00
- Draft1.00
- Proposed1.00
- Pending1.00
- Accepted1.00
- Implemented1.00
- 181.00
- Rejected1.00
- BEP-0611.00
- BEP-0621.00
- BEP-0521.00
- BEP-0561.00
- BEP-0600.99
- BEP-0411.00
- Filesystem API Coherence1.00
- The Function Interface1.00
- Regex1.00
- Errors across bridges0.98
- CSV Standard Library1.00
- Async Iterator Protocol0.99
- Dhilan Shah0.96
- 371.00
- 2d ago1.00
- 2kai2kal20.96
- 口00.68
- 5/26/20261.00
- rossirpaulo1.00
- 口o0.62
- 4/27/20261.00
- 口00.66
- 2d ago0.95
- □60.89
- 5/26/20261.00
- □20.90
- 5d ago1.00
- BEP-0581.00
- BEP-0461.00
- BEP-0161.00
- BEP-0591.00
- Mock1.00
- BEP-0431.00
- Base64 and Base64URL0.98
- BEP-0571.00
- Catch Binding Syntax1.00
- Functions as tools1.00
- Avery Townsend1.00
- Core Type Methods1.00
- Standard Library1.00
- Associated Types for0.99
- kai1.00
- Johnny Godoy0.99
- □130.90
- 2d ago1.00
- 2kai2kai20.99
- rossirpaulo1.00
- Interfaces1.00
- 口00.65
- 4/20/20261.00
- □40.80
- 6/10/20261.00
- □40.73
- 5/7/20261.00
- □40.82
- 5/8/20261.00
- D50.86
- 6/4/20261.00
- BEP-0540.99
- BEP-0551.00
- Range1.00
- Compiler Attributes1.00
- 2kai2kai20.99
- BEP-0291.00
- Mutability Semantics1.00
- UUID Standard Library1.00
- BEP-0451.00
- BEP-0511.00
- Iterators1.00
- 2kai2kai21.00
- □80.80
- 5/22/20261.00
- 2kai2kai20.98
- rossirpaulo1.00
- 2kai2kai21.00
- D10.69
- 5/26/20261.00
- □20.79
- 6/9/20261.00
- □110.84
- 5/8/20261.00
- □50.84
- 6/9/20261.00
- BEP-0531.00
- BEP-0400.99
- Language Semantic Identity0.99
- BEP-0261.00
- BEP-0381.00
- BEP-0491.00
- Middleware Blocks1.00
- and Runtime Trace Model1.00
- print1.00
- Native json Type0.99
- String Interpolation1.00
- aintru1.00
- Work0.98
- AlEr0.88
- 口00.62
- 4/26/20261.00
- □120.94
- rossirpaulo1.00
- 5/21/20261.00
- aaronvg1.00
- □110.92
- 4/24/20261.00
- 口80.85
- 4/29/20261.00
- D60.95
- Antonio Sarosi1.00
- 2d ago1.00
- BEP-0050.96
- Values vs References Across1.00
- the Host Boundary1.00
- BEP-0500.97
- Metrics and Tracing IDs1.00
- BEP-0840.93
- Inferred Visibility (public /0.97
- kai0.97
- BEP-0211.00
- Dates and Times1.00
- BEP-0441.00
- Interfaces1.00
- BAML1.00
- IEnginer0.97
- Id's0.91
- fight slop with slop1.00
- tog0.77
- Engineering the future of Al0.99
- AlEr0.94
- Work0.99
- IDFLAF0.92
-
- BEP-050 Metrics and Tracing IDs0.99
- Copy1.00
- ☆0.80
- Proposed1.00
- AlEngineer0.99
- Shepherds: None assigned1.00
- 0 Add Stance0.91
- History1.00
- World's Fair0.98
- 三 On th0.88
- README1.00
- 461.00
- Summary1.00
- Summar0.99
- Motivatic0.98
- Aggregation1.00
- 21.00
- Probab0.99
- Function Rename Safety1.00
- Any function with a single non-deterministic component anywhere in its call stack becomes1.00
- The ga1.00
- infrast1.00
- Shared LLM-as-Judge1.00
- 41.00
- non-deterministic. Traditional testing (assert output == expected) breaks down — you0.98
- Curren1.00
- need statistical evaluation. Today, evaluation of BAML functions is done entirely outside the0.99
- Multi-Signal Scoring1.00
- Propose1.00
- language: separate eval scripts, YAML configs, dashboard rules. If you rename a function,1.00
- $id1.00
- Multi-Step Evaluation1.00
- the metric binding breaks silently.0.99
- Loca1.00
- Production to Eval0.99
- Scop0.98
- This proposal makes metrics a language-level concept in BAML. It introduces:1.00
- Retroactive Scoring0.99
- set1.00
- Sampling and Cost Control 20.98
- $id — an opt-in trace identity parameter that keeps return types clean, supports0.99
- rossirpaulo1.00
- May 201.00
- parent-child trace trees, and enables retroactive metric attachment1.00
- documenting the dag and that each1.00
- DAG model0.99
- Open Issues1.00
- metric blocks — co-located with the function they measure, type-checked against0.99
- function in the metric block fires1.00
- when their pre reqs are satisfied is a0.99
- risk. humans/agents can get1.00
- Decisions1.00
- its signature, with a reactive DAG model where timing is derived from data0.99
- confused of how async i/o might1.00
- All Comments1.00
- 651.00
- dependencies1.00
- affect this1.00
- Braintru0.96
- Wor1.00
- Al Assistant1.00
- Beta0.99
- assertions1.00
- after blocks on testsets (extending BEP-023) for multi-dimensional batch0.98
- "might affect* knowing that they0.99
- rossirpaulo0.99
- can trust the dag, etc. can be non-1.00
- intuitive, etc1.00
- May 201.00
- BAML0.99
- AlEnginee0.99
- rld's1.00
- fight slop with slop0.98
- tc0.96
- Engineering the future of Al1.00
- Wor1.00
- DUDFLA!0.88
-
- 90.54
- boundary-bot APPMay 18th at 11:47 PM0.98
- AlEngineer0.98
- New BEP Created: BEP-501.00
- World'sFair1.00
- Metrics and Tracing IDs0.98
- Status:draft1.00
- Author: @Vaibhav Gupta0.97
- Shepherds: None assigned1.00
- Last Updated: May 18 at 11:47 PM0.99
- 0 comments | View BEP-50 →0.99
- PRESENTED BY1.00
- beps.boundaryml.com1.00
- BEP Feedback1.00
- Microsoft1.00
- BAML Enhancement Proposals Feedback Application1.00
- 114 replies0.97
- # Also sent to the channel0.98
- Vaibhav Gupta May 18th at 11:53 PM0.98
- recommend taking a look here0.97
- for anyone interested. its not 100% done yet, but the direction +1.00
- many many examples are there in the sub-pages.0.99
- boundary-bot APPMay 20th at 11:40 AM0.98
- @Aaron added a discussion on BEP-50: Metrics and Tracing IDs0.99
- > $id - Trace Identity0.97
- AlEnginee0.98
- i think we should reserve underscore-underscore instead perhaps.1.00
- ntrust1.00
- World's1.00
- $ starts looking wonky0.98
- BAML1.00
- Discussion|May 20 at 11:40 AM0.96
- neer0.94
- sFa1.00
- fight slop with slop0.98
- oget0.96
- Engineering the future of Al1.00
- — AlEnginee0.96
- orld's0.88
- LARE1.00
-
- BEP-001-match0.98
- bep ×0.96
- BEP-002-universal-catch1.00
- AlEngineer1.00
- World's Fair0.99
- BEP-003-safe1.00
- bep1.00
- BEP-004-inferred-visibility-public-private1.00
- >BEP-005-values-vs-references-across-the-host-boundary0.99
- 11.00
- #!/usr/bin/env -S uv run --script0.99
- BEP-006-semantic-streaming-but-better1.00
- 21.00
- # /// script0.98
- BEP-007-typed-throws-contracts-and-inference-alternative-t1.00
- 31.00
- # requires-python = ">=3.10"0.98
- BEP-008-namespaces0.97
- BEP-009-streaming0.98
- 41.00
- # dependencies = ["httpx"]0.99
- PRESENTED BY1.00
- > BEP-010-symmetric-matchcatch-patterns-with-type-pattern-su0.99
- 51.00
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
277 cues· 3,996 words· 21,228 chars
- 0:13 Fighting slop with slop.
- 0:16 My name is Vaibhav, and I'm going to talk about something that is a little, I would say, maybe a little silly at first.
- 0:23 I'm going to show you our team's engineering practices really quickly.
- 0:27 We do no code reviews.
- 0:28 We require every engineer to work on things in parallel.
- 0:32 And we have no standardization how people do AI.
- 0:35 And I know immediately what almost all of you are thinking.
- 0:38 We're probably a Zoom or YC startup.
- 0:41 And I can guarantee you I'm clearly a millennial.
- 0:44 So what do we actually do at our company without code reviews?
- 0:47 Well, about three years ago, we decided to build a programming language.
- 0:52 That's something that has absolutely no room for slop.
- 0:55 It's something that has to work every single time exactly the same way.
- 1:00 It's something that you can't just change a year later or a month later because you made a bad design decision.
- 1:05 You have to be correct.
- 1:06 And for the last three years, we've been in an onslaught of war against slot.
- 1:12 And when I first met this enemy, I went to my great mentor, Slop Sue, and he taught me something.
- 1:19 To defeat the slop, we must become the slop.
- 1:23 So we began, and we prepared, and then we started winning.
- 1:27 So when we think about it, what is slop?
- 1:30 Slop is just any code you don't read.
- 1:32 And whether any of you admit it or not, this is the least amount of slop that your code base will ever have.
- 1:39 Cherish it.
- 1:41 So we started fighting back against the slop, and we started fighting back with slop.
- 1:46 So how do we go ship a stable programming language with these engineering practices?
- 1:51 Well, the first skirmish we ever had was the skirmish of standards.
- 1:55 The hard part about hiring great engineers is you sadly can't tell them what to do.
- 1:59 Some of them want to use Claude, some of them want to use Codex, some of them want to use the latest thing that they just found on Hacker News.
- 2:05 So instead of trying to hold standards in our code base, we did something that is an invariant.
- 2:10 We built an architecture.md file.
- 2:13 Instead of using CloudMD, just pick something that every model can just understand.
- 2:17 This file has to be incredibly small, and it can only have things that will not change for months or for years.
- 2:24 In our case, it's the layers of the compiler.
- 2:26 You go deeper into the compiler, tell the agent to just talk to at least one other person.
- 2:31 That slows it down a little bit.
- 2:33 So now we have standards so anyone can use whatever they want.
- 2:36 But the real foe we faced was actually the battle of design.
- 2:40 Everyone here knows that you have to write perfect design docs.
- 2:43 And we have a very simple rule in our team.
- 2:46 Code can be slopped, writing cannot.
- 2:48 And of course, if I tell every engineer this, they write beautiful writing, and they handwrite everything, they don't use AI.
- 2:52 Well, sadly not.
- 2:54 So we built a design doc tool.
- 2:56 What this design doc tool does, it's a replacement for both Notion and GitHub effectively for design docs.
- 3:01 It allows versioning, commenting, all the stuff you want.
- 3:04 And obviously we do this, people use this.
- 3:05 Well, sadly not.
- 3:06 We built another tool on top of that.
- 3:09 And this tool was a Slack integration for that tool.
- 3:11 Every time a design doc got updated, this channel got notifications.
loading
Chapters
- 0:00 Fighting slop with slop
- 0:27 Code reviews and invariants
- 2:08 Building rules that don't change
- 3:00 Design docs with notifications
- 4:03 CLI tools that catch where things break
- 5:08 Agents reading agent transcripts
- 5:57 Detecting hallucinations and errors
- 9:24 Attacking the foundational layer
- 11:03 Execution traces from first principles
- 14:26 Type safe tools across platforms
- 15:42 Making whole error classes impossible
- 17:57 BAML across languages
- 20:37 Go build the sloppy tools