<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Migration on Programmer.ie: Modern AI programming</title>
    <link>http://programmer.ie/tags/migration/</link>
    <description>Recent content in Migration on Programmer.ie: Modern AI programming</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 07 Sep 2026 13:10:00 +0000</lastBuildDate>
    <atom:link href="http://programmer.ie/tags/migration/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Versioning the Space</title>
      <link>http://programmer.ie/books/embeddings-from-first-principles/17-chapter/</link>
      <pubDate>Mon, 07 Sep 2026 13:10:00 +0000</pubDate>
      <guid>http://programmer.ie/books/embeddings-from-first-principles/17-chapter/</guid>
      <description>&lt;p&gt;&lt;em&gt;Part V — Embedding Spaces Are Not Universal&lt;/em&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-upgrade-that-broke-search-quietly&#34;&gt;The upgrade that broke search quietly&lt;/h2&gt;&#xA;&lt;p&gt;Production runs embedding model v1. A better v2 ships. Someone updates the client library. New documents get v2 vectors; the 10 million existing vectors are still v1. Nothing errors. Queries are embedded with v2 and compared against a mix of v1 and v2 vectors.&lt;/p&gt;&#xA;&lt;p&gt;Recall drops a few points. Nobody notices for a month, because the system still returns ten results and they still look plausible. The v1 and v2 vectors are in different universes (Chapter 16), and half the index is now in the wrong one.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
