<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI on Mansoor</title><link>https://mansoor.io/ai/</link><description>Recent content in AI on Mansoor</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 24 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://mansoor.io/ai/index.xml" rel="self" type="application/rss+xml"/><item><title>Why most RAG implementations fail</title><link>https://mansoor.io/ai/why-rag-fails/</link><pubDate>Fri, 24 Apr 2026 00:00:00 +0000</pubDate><guid>https://mansoor.io/ai/why-rag-fails/</guid><description>&lt;p&gt;The gap between a RAG proof-of-concept and a production system that actually works is wider than most teams expect.&lt;/p&gt;
&lt;p&gt;In my experience, the failures tend to cluster around the same handful of mistakes.&lt;/p&gt;
&lt;h2 id="the-retrieval-unit-is-wrong"&gt;The retrieval unit is wrong&lt;/h2&gt;
&lt;p&gt;Fixed-size chunking is the default because it&amp;rsquo;s easy — split every 500 tokens, done. But documents don&amp;rsquo;t respect token boundaries. A chunk that cuts a table in half, or separates a heading from its body, produces retrievals that are syntactically present but semantically useless.&lt;/p&gt;</description></item></channel></rss>