<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Adaptation on Programmer.ie: Modern AI programming</title>
    <link>http://programmer.ie/tags/adaptation/</link>
    <description>Recent content in Adaptation on Programmer.ie: Modern AI programming</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 14 Sep 2026 05:00:16 +0100</lastBuildDate>
    <atom:link href="http://programmer.ie/tags/adaptation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Learning From Experience</title>
      <link>http://programmer.ie/books/memory/16-chapter/</link>
      <pubDate>Mon, 14 Sep 2026 05:00:16 +0100</pubDate>
      <guid>http://programmer.ie/books/memory/16-chapter/</guid>
      <description>&lt;p&gt;Chapter 15 asked how a long-lived memory system keeps accumulated history manageable without destroying what later work may still need. That remains memory management: the system changes which retained experiences are represented, available, or allowed to compete.&lt;/p&gt;&#xA;&lt;p&gt;This chapter crosses a different boundary.&lt;/p&gt;&#xA;&lt;p&gt;Suppose the system performs a migration, observes that it succeeded, and then changes what it will retrieve next time. Suppose it notices that the same sequence of checked actions has worked repeatedly and turns that sequence into a reusable method. The system is no longer only asking what the past contains or which part matters now.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
