Stop Fine-Tuning to Fix Retrieval Problems — Anant Srivastava
by AI Engineer20:12 long1.9K views
Why watchA 20-minute talk for engineers about to fine-tune a model to fix wrong answers: a clear rule for what belongs in the prompt, in retrieval and in weights.
What this video covers
Anant Srivastava, principal technologist for data and AI platforms at Oracle, gave this talk at the AI Engineer World's Fair 2026 in San Francisco. His question is where an AI product's knowledge should live: in the prompt, in memory (retrieval), or in the model's weights. He treats these as three tools for three jobs, and argues against climbing from one to the next whenever answers go wrong.
The opening chapters (0:00 to 2:00) set up the problem. Teams rarely make this choice on purpose; months of ordinary product work make it for them, and every prompt edit, indexed document and training sample is an architecture decision. At 2:40 he describes a support assistant that kept inventing product names after a fine-tune, and at 4:34 he explains how that kind of system piles up by accident.
The middle of the talk gives a diagnostic for each layer. From 5:14, the prompt is for small, stable behavior, with an example support agent prompt at 5:59. Memory follows at 6:59: knowledge that is current, large, citable or access-controlled belongs there. He covers the wrong job for memory (8:09), why access control sits in memory (8:49), and a code assistant example (9:14) with chunking and metadata for code RAG (10:08).
Weights come up at 11:23. His rule is that only reflexes that have stopped changing go into the model. The fine-tuning mistake is at 12:28, cases where fine-tuning works start at 13:53, and a medical coding example at 15:08 shows fine-tuning a reflex. A short section at 16:13 asks whether a problem is about capability or cost.
A decision table at 16:58 pulls the three layers together. From 17:33 he describes a circulating architecture, where knowledge moves between context, memory and weights over time and the agent gets better by doing its job. The final chapter, at 19:27, is titled "The model is the easy part".
The talk suits engineers and tech leads deciding between prompting, RAG and fine-tuning, or anyone who has watched a fine-tune make an assistant less accurate.
Written by HuiaHub from the creator's title, description and chapters. All credit for the video goes to AI Engineer.
Key takeaways
- Prompt, memory and weights are three tools for different jobs, not steps on a ladder.
- Use the prompt for small, stable behavior rather than facts.
- Put current, large, citable or access-controlled knowledge in memory.
- Fine-tune weights for reflexes that have stopped changing, never for facts.
- Every prompt edit, indexed document and training sample is an architecture decision.
- Knowledge can move between context, memory and weights as a system matures.
Chapters
- 0:00Where should knowledge live? (opens YouTube at this moment)
- 0:15The real engineering problem (opens YouTube at this moment)
- 0:50Three tools, not a ladder (opens YouTube at this moment)
- 1:20How teams decide by accident (opens YouTube at this moment)
- 2:00Every edit is an architecture decision (opens YouTube at this moment)
- 2:40A support assistant goes wrong (opens YouTube at this moment)
- 4:34Accumulated, not designed (opens YouTube at this moment)
- 5:14Prompt: behavior, not facts (opens YouTube at this moment)
- 5:59Example: a support agent prompt (opens YouTube at this moment)
- 6:59Memory: current, large, citable (opens YouTube at this moment)
- 8:09The wrong job for memory (opens YouTube at this moment)
- 8:49Access control belongs in memory (opens YouTube at this moment)
- 9:14Example: a code assistant (opens YouTube at this moment)
- 10:08Chunking and metadata for code RAG (opens YouTube at this moment)
- 11:23Weights: what has stopped changing (opens YouTube at this moment)
- 12:28The fine-tuning mistake (opens YouTube at this moment)
- 13:53When fine-tuning works (opens YouTube at this moment)
- 15:08Medical coding: fine-tune the reflex (opens YouTube at this moment)
- 16:13Capability or cost? (opens YouTube at this moment)
- 16:58The decision table (opens YouTube at this moment)
- 17:33A circulating architecture (opens YouTube at this moment)
- 19:27The model is the easy part (opens YouTube at this moment)
More videos
22:46intermediateHow Inference Keeps Up with Our Insatiable Need for Tokens — Cerebras & Gimlet Labs
A 22-minute AI Engineer talk for inference engineers that covers runtime tricks like paged KV cache and chunked prefill, then system-level disaggregation and kernel-writing agents.
AI Engineer · 1.2K views ·
14:22intermediateSandboxes Aren't Optional: 4 Ways to Isolate Coding Agents — Robert Brennan, OpenHands
A 14-minute talk from the OpenHands CEO comparing four ways to sandbox coding agents, for developers who run agents with broad permissions.
AI Engineer · 3.9K views ·
19:17intermediateStop Renting Intelligence: The Train-to-Deploy Loop for Specialized AI — Fireworks AI
A 19-minute Fireworks AI talk on training open models on your own data and redeploying them in a continuous loop, for teams weighing closed-model costs.
AI Engineer · 6.1K views ·
14:07intermediateThree Questions Every Agent Engineer Should Be Able To Answer
A 14-minute LangChain talk on finding, reproducing and fixing agent failures using production traces, for engineers who run agents in production.
LangChain · 8.1K views ·