Retrieval first is the right focus
Our RAG demo looked fine until we measured recall. This course showed us exactly where it was failing.
Browse
Build retrieval augmented generation with embeddings, pgvector, hybrid search and reranking, and measure it properly before you ship
Created by Elena Petrova
Retrieval augmented generation, usually called RAG, is the most common way to make a language model answer questions about your own documents: handbooks, product docs, contracts, support articles. Instead of hoping the model knows the answer, you search your documents first and give the model the relevant passages to answer from.
A RAG demo takes an afternoon. A RAG system that people trust takes much more care. Most failures come from retrieval, not generation: the right passage was never found, was split in half or was buried under near duplicates. This course focuses on getting retrieval right and proving it with measurements.
Askdocs, a question answering service over a company knowledge base of a few thousand pages, with citations, permission aware search, fresh content and an evaluation suite.
You should be comfortable with Python, SQL basics and calling an LLM API. Experience with any web framework helps for the final section.
AI engineer teaching prompting, LLM APIs and retrieval apps that work in practice
I build applications on top of large language models: assistants, document search and internal tools that save teams real time. I have learned most of what I teach by shipping features, watching them fail in odd ways and fixing them.
My courses are hands on and vendor neutral. We use the APIs from several model providers, compare results, and write small evaluations so you can tell whether a change helped.
I care about the unglamorous parts: cost, latency, privacy and knowing when a plain search or a simple rule is better than a model.
Our RAG demo looked fine until we measured recall. This course showed us exactly where it was failing.
Filtering by access group inside the query was exactly the guidance our security team wanted.
Adding keyword search and a reranker fixed most of our failures with product codes.
Great to keep everything in PostgreSQL. I would like more on scaling to millions of chunks.
Heading paths in chunks were a small change with a big effect on our results.
Separating retrieval metrics from answer metrics changed how our team debugs RAG.
A lot of material in each lesson. I needed to rewatch the evaluation part, but it paid off.