<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0"
     xmlns:atom="http://www.w3.org/2005/Atom"
     xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Neelansh Khare — Blog</title>
    <link>https://neelanshkhare.github.io/new-portfolio/blog</link>
    <description>Weekly updates on research, engineering, and side projects from Neelansh Khare.</description>
    <language>en-us</language>
    <atom:link href="https://neelanshkhare.github.io/new-portfolio/rss.xml" rel="self" type="application/rss+xml" />
    <lastBuildDate>Sun, 29 Mar 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>The &apos;U-Shape&apos; Reality &amp; Query Stability</title>
      <link>https://neelanshkhare.github.io/new-portfolio/blog/weekly-update-week-2</link>
      <guid isPermaLink="true">https://neelanshkhare.github.io/new-portfolio/blog/weekly-update-week-2</guid>
      <pubDate>Sun, 29 Mar 2026 00:00:00 GMT</pubDate>
      <description>Reproducing the &apos;Lost in the Middle&apos; U-shaped performance curve and probing query stability in retrieval systems.</description>
      <content:encoded><![CDATA[<p>This week felt like the moment the two separate threads of my research finally started to pull together into a single, cohesive story. The big 'Aha!' moment came when I successfully reproduced the 'Lost in the Middle' U-shaped performance curve in my position-controlled study.</p>
<p>It's one thing to read about models failing to utilize information in the middle of a long context; it's another thing entirely to see a heuristic model hit 100% accuracy at the edges and a flat 0% in the center. It's a stark reminder that in the world of LLMs, context isn't just about capacity—it's about attention and positioning.</p>
<p>Meanwhile, on the RAG saturation front, I've been obsessing over query stability. I built a QueryPhrasingShiftGenerator to see how fragile our retrieval systems actually are. It turns out that small, semantic shifts in how we ask a question can lead to wildly different retrieval results. If our retrieval is unstable, our downstream generation is built on sand.</p>
<p>What I'm learning is that these two problems—retrieval saturation and position sensitivity—are actually two sides of the same coin. As we scale up the number of retrieved passages, we're essentially forcing more and more critical evidence into that 'dead zone' in the middle of the prompt. We're not just fighting for better retrieval; we're fighting for model attention.</p>]]></content:encoded>
    </item>
    <item>
      <title>Foundations &amp; The RAG Baseline</title>
      <link>https://neelanshkhare.github.io/new-portfolio/blog/weekly-update-week-1</link>
      <guid isPermaLink="true">https://neelanshkhare.github.io/new-portfolio/blog/weekly-update-week-1</guid>
      <pubDate>Sun, 22 Mar 2026 00:00:00 GMT</pubDate>
      <description>Kicking off two parallel research tracks: a RAG baseline and a position-controlled reproduction of long-context evaluations.</description>
      <content:encoded><![CDATA[<p>I've officially kicked off two parallel research tracks this week, and the initial scaffolding phase has already been so informative.</p>
<p>The biggest thing I noticed while setting up the baseline for my independant research paper is how quickly evaluation metrics like Exact Match and token-level F1 become your best friends. Without a rigorous feedback loop, you're just guessing. I spent a lot of time this week making sure my sanity checks were actually sane before I start the massive scale-sweeps next week.</p>
<p>On the reproduction side, I'm deep-diving into the mechanics of position-controlled experiments. By breaking down the context into 'buckets' (beginning, early-middle, etc.), I'm preparing to test exactly where models start to lose the plot. It's making me much more conscious of how I structure prompts in my other projects.</p>
<p>It's a bit of a juggling act, but I'm already seeing where these paths might cross. Starting with clean, reproducible baselines is slower, but it's the only way to build something that actually stands up to scrutiny.</p>]]></content:encoded>
    </item>
    <item>
      <title>Welcome to my Blog</title>
      <link>https://neelanshkhare.github.io/new-portfolio/blog/welcome</link>
      <guid isPermaLink="true">https://neelanshkhare.github.io/new-portfolio/blog/welcome</guid>
      <pubDate>Sun, 08 Feb 2026 00:00:00 GMT</pubDate>
      <description>A quick note on why this blog exists and what I plan to write about.</description>
      <content:encoded><![CDATA[<p>Welcome to my personal blog. This is where I'll be sharing my thoughts, updates, and technical deep dives.</p>
<p>I plan to update this space weekly with new content regarding software engineering, backend systems, and my ongoing projects.</p>
<p>Stay tuned for more!</p>]]></content:encoded>
    </item>
  </channel>
</rss>
