<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tables on Programmer.ie: Modern AI programming</title>
    <link>http://programmer.ie/tags/tables/</link>
    <description>Recent content in Tables on Programmer.ie: Modern AI programming</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 23 Sep 2026 05:00:18 +0100</lastBuildDate>
    <atom:link href="http://programmer.ie/tags/tables/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Representation Is Part of Context</title>
      <link>http://programmer.ie/books/context/18-chapter/</link>
      <pubDate>Wed, 23 Sep 2026 05:00:18 +0100</pubDate>
      <guid>http://programmer.ie/books/context/18-chapter/</guid>
      <description>&lt;p&gt;Two bundles carry the same migration facts. The first is prose: the migration uses PostgreSQL, its identifier is 01947, it remains blocked by test suite A, the team rejected the SQLite fallback after the staging incident. The second is a labelled record with the same four facts in named fields. Asked which identifier belongs to the unresolved migration, the model answers from the record and fumbles in the prose — the digits sit mid-sentence beside another number and bind to the wrong noun. Asked why the SQLite fallback was rejected, the model answers from the prose and starves on the record, whose reason field kept the headline and dropped the causal qualification. Nothing was selected differently. Everything was represented differently. Selection finished, and the context still was not the same.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
