hardCognitionGitHubAnthropic

How do you build RAG over a large code repository so an agent can answer questions and edit code?

Splitting source files every 500 characters cuts functions in half and destroys retrieval. The signal is chunking on syntax, retrieving by symbol and dependency, and combining lexical exact-match with semantic search the way code search actually needs.

Updated Aug 2026 · Grounded in real Applied AI Engineer interview loops and written to a senior-engineer editorial bar.

Unlock the other 754 answers · ₹2,000 / $25includes both full courses · progress stays saved · 6 months · one payment · no auto-renew

LEARN THE BACKGROUND

No lesson covers this question directly yet. These teach the surrounding topic from the beginning.

Agent Engineering·Agents in the interviewPremium12mThe sentences that mark someone who has run oneThe final lesson. Six specific things a candidate says that could only come from operating an agent rather than building one, and the three claims that reliably mark the opposite.Applied AI Engineering·The interviewPremium12mTurning this course into a study planA concrete four-week plan mapping the seven modules onto the question bank, plus what to do differently if your interview is next week rather than next month.

UP NEXT ON YOUR JOURNEY

Next in this trackHow do you do incremental indexing for a RAG system with constant document churn, without a nightly full rebuild?Next in this trackHow do you verify that an answer's citations actually support its claims (grounding verification)?Next in this trackHow do you measure faithfulness (hallucination rate) in a RAG system, and what makes it hard to score?

DISCUSSION · 0

No comments yet — be the first to share your approach.