<?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>Llm on lgcode</title>
    <link>https://blog.lgcode.me/tags/llm/</link>
    <description>Recent content in Llm on lgcode</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 29 Aug 2026 09:00:00 -0300</lastBuildDate>
    <atom:link href="https://blog.lgcode.me/tags/llm/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Cache That Cancels Your Improvement</title>
      <link>https://blog.lgcode.me/posts/the-cache-that-cancels-your-improvement/</link>
      <pubDate>Sat, 29 Aug 2026 09:00:00 -0300</pubDate>
      <guid>https://blog.lgcode.me/posts/the-cache-that-cancels-your-improvement/</guid>
      <description>I improved a matching pipeline, measured the improvement, deployed it, and reprocessed the backlog. The backlog reproduced every old decision exactly. The cache was keyed on the input and stored the verdict.</description>
    </item>
    <item>
      <title>The Demo Video Was the Easy Part</title>
      <link>https://blog.lgcode.me/posts/the-demo-video-was-the-easy-part/</link>
      <pubDate>Sat, 08 Aug 2026 09:00:00 -0300</pubDate>
      <guid>https://blog.lgcode.me/posts/the-demo-video-was-the-easy-part/</guid>
      <description>A margin that was arithmetically correct and substantively false, confidence scores from a model that wasn&amp;#39;t deployed, and one in five invoice lines failing its own arithmetic. Generating the video took minutes. Making it true took two days.</description>
    </item>
    <item>
      <title>What Dogfooding an MCP Server Taught Me About Tool Output</title>
      <link>https://blog.lgcode.me/posts/mcp-tool-output-design/</link>
      <pubDate>Mon, 03 Aug 2026 10:00:00 -0300</pubDate>
      <guid>https://blog.lgcode.me/posts/mcp-tool-output-design/</guid>
      <description>A filter that discarded the answer, a retry that couldn&amp;#39;t work, a partial result posing as a total, and cached prices with no freshness signal. All four found in one live session, all four the same class of mistake.</description>
    </item>
  </channel>
</rss>
