~/talk

Verification, Cost, and Speed: What's Next for AI Coding at Scale

links:none on file
links:none on file
links:none on file
links:none on file
links:none on file
links:none on file
slides:none on file

Panel distills practical claims: verification often costs more than generation so teams use AI to produce test harnesses and deterministic checks (recipe runs validate patch files) and treat CI compute and review capacity as real bottlenecks. Scale tactics include hierarchical indexing of a code estate and projection to CSV; one cited estate is ~4.5 billion lines and context windows are ~1M tokens. Budgeting matters — examples: 10 billion tokens in a month and $2k/month per heavy developer — so teams add harness engineering, telemetry, and staged rollouts.

AI-written summary · about

  1. 0:00Introduction and panel setup
  2. 2:10Why AI coding at scale matters
  3. 3:38Verification techniques for large changes
  4. 14:34Handling massive codebases
  5. 21:57Speeding up developer workflows
  6. 34:44Managing AI token costs
  7. 47:15Ensuring code accuracy at scale
  8. 56:24Closing remarks and Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.