39 minutesIntroducing RAG 2.0: Agentic RAG + Knowledge Graphs (FREE Template)
Compare agentic retrieval and graph retrieval in a concrete implementation.
AI Engineer. Douwe Kiela led the original RAG paper at FAIR and now ships RAG into regulated enterprises. The talk is mostly about what stops working at scale — chunking strategies that don't survive 100k documents, "accuracy is table stakes, inaccuracy is the real problem," and why attribution and observability matter more than the embedding model. Good calibration before re-reading the article's eval and monitoring sections.
Strong production cautionary material. Use it to pressure-test architecture decisions, especially permissions, attribution, observability and user trust, before debating embedding-model minutiae.
Understand what breaks when RAG moves into regulated, high-stakes enterprise use.
Know the basic RAG pipeline and why attribution matters.
Last reviewed: May 18, 2026
Continue through the same learning path with the next curated companion videos.
39 minutesCompare agentic retrieval and graph retrieval in a concrete implementation.
13 minutesChoose between prompt engineering, RAG, fine-tuning or a combination based on the actual failure mode.
157 minutesYou will be able to run quantisation, LoRA and QLoRA fine-tunes end to end on hardware most developers already have.
Hand-picked external courses that go deeper on this topic.
Emory University Goizueta Business School faculty
The deeper, university-level counterpart to our beginner HubSpot marketing pick — Emory's business-school treatment goes past 'how to prompt' into training generative models for brand-specific output, the purchase-funnel economics of AI-generated content, and a full module of genuine skepticism about when generative AI is and isn't worth using in marketing.
IBM AI Academy
The genAI-era answer to the executive-strategy question. Three short courses aimed squarely at business leaders — no technical background required — on where generative AI creates value, how to govern it responsibly, and how to turn a vague "we should use AI" into a concrete, defensible use case. Rated 4.6 across ~700 reviews. Best taken before your next AI budget decision.