<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rag on EBKAC.ORG</title>
    <link>https://ebkac.org/tags/rag/</link>
    <description>Recent content in Rag on EBKAC.ORG</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Thu, 19 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ebkac.org/tags/rag/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building BuchhalterPython: Architecture Before the First Commit (Part 2)</title>
      <link>https://ebkac.org/blog/2026-03-19-buchhalter-architecture-decisions/</link>
      <pubDate>Thu, 19 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://ebkac.org/blog/2026-03-19-buchhalter-architecture-decisions/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;Part 2 of the BuchhalterPython series.&lt;/strong&gt; &lt;a href=&#34;https://ebkac.org/blog/2026-03-18-buchhalter-agentic-setup/&#34;&gt;Part 1&lt;/a&gt; covers how we set up agentic infrastructure — six specialised agents, golden standards, and token optimisation — before writing any application code.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;We spent a full day on architecture before writing a single line of business logic. No features, no endpoints, no database schemas. Just decisions. By the end of that day, we had five architectural choices that each prevented at least one production failure. Three of those failures would have been silent.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Lernreise 4/7: The Grand Plan: RAG, Vectors, and a 7-Cent Bargain</title>
      <link>https://ebkac.org/blog/lernreise-04-rag-architecture/</link>
      <pubDate>Sat, 14 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://ebkac.org/blog/lernreise-04-rag-architecture/</guid>
      <description>&lt;p&gt;Before touching a single node in n8n, I asked Gemini a sensible question: for this problem, is n8n or Python the better choice?&lt;/p&gt;&#xA;&lt;p&gt;Gemini said n8n, clearly and confidently. It was the right tool for orchestration, it said. Visual workflows, lower barrier, easier to iterate. Perfect for this use case.&lt;/p&gt;&#xA;&lt;p&gt;I want to note this for the record, because it becomes relevant later.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;The architecture I had in mind had several parts.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
