<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Llm on Hullabalooing</title>
    <link>https://cruver.ai/tags/llm/</link>
    <description>Recent content in Llm on Hullabalooing</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 00:00:00 -0400</lastBuildDate>
    <atom:link href="https://cruver.ai/tags/llm/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Software for an Audience of One</title>
      <link>https://cruver.ai/writing/posts/software-for-an-audience-of-one/</link>
      <pubDate>Tue, 06 Oct 2026 00:00:00 -0400</pubDate>
      <guid>https://cruver.ai/writing/posts/software-for-an-audience-of-one/</guid>
      <description>&lt;p&gt;For most of the history of software, an application existed because enough people wanted it to pay for the time it took to build. A tool that only one person needed usually didn&amp;rsquo;t get written, unless that person happened to be a programmer with a lot of spare evenings. Everyone else adapted to whatever the market offered.&lt;/p&gt;&#xA;&lt;p&gt;That has changed. With modern LLM coding tools, a person with a clear picture of the application they want can build it, even if they will be its only user. I think of it as custom software on demand: not a product with a market, but a tool made for one person&amp;rsquo;s way of working. I&amp;rsquo;ve been building software this way for most of this year, and I think it is one of the more important things these tools make possible.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Task-Decoupled Agents: Breaking the Monolithic Context Problem</title>
      <link>https://cruver.ai/writing/posts/task-decoupled-agents-1769113856/</link>
      <pubDate>Thu, 22 Jan 2026 13:30:56 +0000</pubDate>
      <guid>https://cruver.ai/writing/posts/task-decoupled-agents-1769113856/</guid>
      <description>&lt;p&gt;A recent paper from Tsinghua and Renmin University caught my attention: &lt;a href=&#34;https://arxiv.org/abs/2601.07577&#34;&gt;Task-Decoupled Planning for Long-Horizon Agents&lt;/a&gt;. The core insight resonated with a problem I&amp;rsquo;ve been wrestling with on a Java code modernization project at work, and I think the pattern deserves more attention.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-entangled-context-problem&#34;&gt;The Entangled Context Problem&lt;a class=&#34;anchor&#34; href=&#34;#the-entangled-context-problem&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;Most LLM agent architectures fall into two camps: step-wise planning (reactive, one step at a time) or one-shot planning (generate the whole plan upfront). Both share a fatal flaw: they maintain a monolithic reasoning context that spans the entire task history.&lt;/p&gt;</description>
    </item>
    <item>
      <title>vLLM Inference on MI60</title>
      <link>https://cruver.ai/gpu-ai/posts/vllm-inference-mi60/</link>
      <pubDate>Wed, 21 Jan 2026 00:00:00 -0700</pubDate>
      <guid>https://cruver.ai/gpu-ai/posts/vllm-inference-mi60/</guid>
      <description>&lt;p&gt;Production inference using vLLM with tensor parallelism across dual MI60 GPUs.&lt;/p&gt;&#xA;&lt;h2 id=&#34;why-vllm&#34;&gt;Why vLLM?&lt;a class=&#34;anchor&#34; href=&#34;#why-vllm&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;After evaluating Ollama, llama.cpp, and vLLM for MI60 inference, &lt;strong&gt;vLLM&lt;/strong&gt; emerged as the best choice:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tensor Parallelism&lt;/strong&gt;: Native support for splitting large models across multiple GPUs. With dual MI60s (64GB total), I can run 70B parameter models that wouldn&amp;rsquo;t fit on a single GPU.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;PagedAttention&lt;/strong&gt;: More efficient memory management, allowing higher GPU utilization (90%) without OOM errors.&lt;/p&gt;</description>
    </item>
    <item>
      <title>An Affordable AI Server</title>
      <link>https://cruver.ai/gpu-ai/posts/an-affordable-ai-server-1768704467/</link>
      <pubDate>Sat, 17 Jan 2026 00:00:00 -0700</pubDate>
      <guid>https://cruver.ai/gpu-ai/posts/an-affordable-ai-server-1768704467/</guid>
      <description>&lt;p&gt;Two AMD MI60s from eBay cost me about $1,000 total and gave me 64GB of VRAM. That&amp;rsquo;s enough to run Llama 3.3 70B at home with a 32K context window.&lt;/p&gt;&#xA;&lt;p&gt;When I started looking into running large language models locally, the obvious limiting factor was VRAM. Consumer GPUs top out at 24GB, and that&amp;rsquo;s on an RTX 4090 at the high end. I wanted to run 70B parameter models locally, on hardware I own.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
