<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Frederik Rybansky — Writing</title>
    <link>https://rybansky.info/writing/</link>
    <description>Notes on AI infrastructure, AI agents, retrieval and chatbots by Frederik Rybansky.</description>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://rybansky.info/feed.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>How to Introduce AI Agents Without Burning the IT Budget</title>
      <link>https://rybansky.info/writing/ai-agents-in-enterprise/</link>
      <guid isPermaLink="true">https://rybansky.info/writing/ai-agents-in-enterprise/</guid>
      <pubDate>Wed, 18 Feb 2026 00:00:00 GMT</pubDate>
      <description>Enterprise agent projects usually fail for organisational reasons, not technical ones. Here is the rollout sequence that has worked for me — narrow, measured, and reversible at every step.</description>
    </item>
    <item>
      <title>RAG or Fine-Tuning? Choosing the Right Approach for Knowledge</title>
      <link>https://rybansky.info/writing/rag-vs-fine-tuning/</link>
      <guid isPermaLink="true">https://rybansky.info/writing/rag-vs-fine-tuning/</guid>
      <pubDate>Thu, 22 Jan 2026 00:00:00 GMT</pubDate>
      <description>Fine-tuning gets attention and a budget line. Retrieval gets results. For anything that changes — prices, policies, inventory, specs — the answer is almost always retrieval.</description>
    </item>
    <item>
      <title>What an AI Chatbot on a Website Actually Returns</title>
      <link>https://rybansky.info/writing/ai-chatbot-roi/</link>
      <guid isPermaLink="true">https://rybansky.info/writing/ai-chatbot-roi/</guid>
      <pubDate>Tue, 09 Dec 2025 00:00:00 GMT</pubDate>
      <description>Chatbots fail commercially in one specific way: nobody measured the right thing, so the pilot survived on conversation counts while support volume stayed exactly where it was.</description>
    </item>
  </channel>
</rss>
