<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Domain Knowledge on Andre&#39;s blog</title>
    <link>https://www.baryudin.com/tags/domain-knowledge/</link>
    <description>Recent content in Domain Knowledge on Andre&#39;s blog</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Sat, 19 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.baryudin.com/tags/domain-knowledge/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>From Frameworks to Prompts: Rethinking Reusable Software in the Age of AI</title>
      <link>https://www.baryudin.com/blog/ai-libraries/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.baryudin.com/blog/ai-libraries/</guid>
      <description>&lt;p&gt;There was a time, not so very long ago, when building software meant assembling it by hand from reusable parts. If you wanted to launch a shopping website, you did not begin with a blank text editor and a prayer. You reached for a framework. You configured a catalogue module, bolted on a shopping cart, wired up a checkout pipeline, and spent a wearying number of evenings squinting at documentation for payment gateway integrations. Behind the customer-facing storefront sat an equally demanding apparatus: order queues, label printing, returns handling, customer history, discount engines, promotional rules. The list of concerns was long, and each one needed attention before a single sale could be completed.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
