<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Pradhumn Gupta</title>
    <link>https://pradhumngupta.com</link>
    <description>I build production RAG, agentic search, and the systems that make LLMs actually work in the real world.</description>
    <language>en</language>
    <item>
      <title>Why RAG fails in production — and where</title>
      <link>https://pradhumngupta.com/writing/why-rag-fails-in-production</link>
      <guid>https://pradhumngupta.com/writing/why-rag-fails-in-production</guid>
      <description>When RAG breaks, the model usually isn&apos;t the problem — retrieval is, about 73% of the time. Here&apos;s the real failure map and what to fix first.</description>
      <pubDate>Wed, 08 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Why I don&apos;t use LangChain in production RAG</title>
      <link>https://pradhumngupta.com/writing/why-i-dont-use-langchain-in-production</link>
      <guid>https://pradhumngupta.com/writing/why-i-dont-use-langchain-in-production</guid>
      <description>Frameworks are great for a demo. In production, the abstraction you can&apos;t see into costs more than it saves.</description>
      <pubDate>Wed, 08 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>When NOT to use RAG (RAG vs fine-tuning vs prompting)</title>
      <link>https://pradhumngupta.com/writing/when-not-to-use-rag</link>
      <guid>https://pradhumngupta.com/writing/when-not-to-use-rag</guid>
      <description>RAG became the default reflex for every LLM problem. Often it&apos;s the wrong tool. A straight decision framework for RAG vs fine-tuning vs just prompting.</description>
      <pubDate>Wed, 08 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>A reference architecture for production RAG</title>
      <link>https://pradhumngupta.com/writing/production-rag-reference-architecture</link>
      <guid>https://pradhumngupta.com/writing/production-rag-reference-architecture</guid>
      <description>The stages every production RAG system needs — indexing, query-time retrieval, and always-on evaluation — and how to order them.</description>
      <pubDate>Wed, 08 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Naive retrieve-then-generate isn&apos;t enough for production</title>
      <link>https://pradhumngupta.com/writing/naive-rag-is-not-enough</link>
      <guid>https://pradhumngupta.com/writing/naive-rag-is-not-enough</guid>
      <description>The 5-line RAG baseline is great for a demo and fragile in production. Here&apos;s where it breaks and the upgrade path that fixes it.</description>
      <pubDate>Wed, 08 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The single most useful log line in a RAG system</title>
      <link>https://pradhumngupta.com/writing/most-useful-log-line-in-rag</link>
      <guid>https://pradhumngupta.com/writing/most-useful-log-line-in-rag</guid>
      <description>If you log one thing in your RAG pipeline, log the final assembled prompt. It&apos;s the fastest path from &apos;bad answer&apos; to root cause.</description>
      <pubDate>Wed, 08 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Hybrid search for RAG: combining BM25 and dense vectors with RRF</title>
      <link>https://pradhumngupta.com/writing/hybrid-search-bm25-dense-rrf</link>
      <guid>https://pradhumngupta.com/writing/hybrid-search-bm25-dense-rrf</guid>
      <description>Why you can&apos;t average keyword and vector scores — and how Reciprocal Rank Fusion combines them for an 8–15% accuracy gain.</description>
      <pubDate>Wed, 08 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to reduce RAG hallucinations: a practical checklist</title>
      <link>https://pradhumngupta.com/writing/how-to-reduce-rag-hallucinations</link>
      <guid>https://pradhumngupta.com/writing/how-to-reduce-rag-hallucinations</guid>
      <description>Most RAG hallucinations are retrieval bugs in disguise. A concrete checklist to cut them — grounding, retrieval quality, and faithfulness checks.</description>
      <pubDate>Wed, 08 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to debug a RAG pipeline that returns wrong answers</title>
      <link>https://pradhumngupta.com/writing/how-to-debug-a-rag-pipeline</link>
      <guid>https://pradhumngupta.com/writing/how-to-debug-a-rag-pipeline</guid>
      <description>A step-by-step debug order for bad RAG answers — start with the assembled prompt, not the model. Most bugs are retrieval, not generation.</description>
      <pubDate>Wed, 08 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to choose chunk size and overlap for RAG</title>
      <link>https://pradhumngupta.com/writing/how-to-choose-chunk-size-for-rag</link>
      <guid>https://pradhumngupta.com/writing/how-to-choose-chunk-size-for-rag</guid>
      <description>Start at 512 tokens with light overlap, then tune by query type. A practical, benchmark-backed guide to chunk size for retrieval.</description>
      <pubDate>Wed, 08 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>RAG chunking strategies: a practical reference</title>
      <link>https://pradhumngupta.com/writing/rag-chunking-strategies-reference</link>
      <guid>https://pradhumngupta.com/writing/rag-chunking-strategies-reference</guid>
      <description>The common chunking approaches for retrieval, when each one helps, and the tradeoffs — a quick reference you can come back to.</description>
      <pubDate>Mon, 06 Jul 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>