<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Agents on George&#39;s Blog</title>
    <link>https://blog.georgefabish.com/tags/agents/</link>
    <description>Recent content in Agents on George&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Wed, 29 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.georgefabish.com/tags/agents/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Server LLM Map</title>
      <link>https://blog.georgefabish.com/posts/server-llm-map/</link>
      <pubDate>Wed, 29 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.georgefabish.com/posts/server-llm-map/</guid>
      <description>&lt;p&gt;Self-hosting a Linux server can involve many repetitive and time-consuming tasks. When I first set up my Ubuntu server, I would spend much of the day searching Stack Overflow for various bash commands. Then LLMs came onto the scene. They made this task much more ergonomic. Still, there was friction. Part of this was due to early LLMs being less reliable, but most of the friction came from the LLM not having the context it needed. So each chat would start with a litany of system info, apps that were installed, troubleshooting steps that had already been tried, etc. My approach has now evolved to using a structured folder documentation repo. This started by coming up with a schema which basically became something like:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
