~/talk

RAG: Tricks from the trenches.

links:none on file
slides:none on file

Practical RAG lessons: changing one embedding model raises relevant-retrieval from about 16.5% to 62.89% (roughly a 300% gain), so embedding choice matters more than which vector DB is used. Examples use SentenceTransformers, LanceDB for a 25-line RAG, scikit-learn clustering for representative summaries, GPT-3.5 Turbo with Pydantic-style structured outputs for verifiable facts, and BM25 proved superior in one eight-month production rollout. Production advice: start simple, log queries and contexts, iteratively fix the hardest failures.

AI-written summary · about

  1. 0:00Introduction and speaker background
  2. 1:49What is RAG and why it matters
  3. 6:23Why your embedding choice sucks
  4. 9:38Structured outputs for sanity
  5. 14:33Exploding context and summaries
  6. 18:47Ugly production data realities
  7. 21:16Is your system actually any good?
  8. 24:09Final thoughts and resources
  9. 25:13Q&A session
~/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.