<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Knowledge Work on Programmer.ie: Modern AI programming</title>
    <link>http://programmer.ie/tags/knowledge-work/</link>
    <description>Recent content in Knowledge Work on Programmer.ie: Modern AI programming</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 14 Sep 2026 05:00:04 +0100</lastBuildDate>
    <atom:link href="http://programmer.ie/tags/knowledge-work/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Scrum Built the Training Set</title>
      <link>http://programmer.ie/books/applied-ai/04-chapter/</link>
      <pubDate>Mon, 14 Sep 2026 05:00:04 +0100</pubDate>
      <guid>http://programmer.ie/books/applied-ai/04-chapter/</guid>
      <description>&lt;p&gt;&lt;em&gt;Part 1 — Where You Stand&lt;/em&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;an-uncomfortable-piece-of-bookkeeping&#34;&gt;An uncomfortable piece of bookkeeping&lt;/h2&gt;&#xA;&lt;p&gt;Software engineering was the first knowledge profession to be substantially automated by language models. The usual explanation is that code is logical and therefore tractable for a machine.&lt;/p&gt;&#xA;&lt;p&gt;That explanation is wrong, and believing it will cost you, because it points at the wrong property when you go looking for the next domain.&lt;/p&gt;&#xA;&lt;p&gt;Here is what actually happened. For roughly two decades the industry adopted a family of methodologies — Agile, Scrum, Kanban, whatever your organization called its version — that mandated a particular discipline of record-keeping. Work had to be:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
