<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>LLMs on Alexander Arvidsson</title>
    <link>/tags/llms/</link>
    <description>Recent content in LLMs on Alexander Arvidsson</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    
    <lastBuildDate>Tue, 28 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/llms/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>When the Sycophant Is Reviewing the Sycophant</title>
      <link>/posts/sycophant-reviewing-the-sycophant/</link>
      <pubDate>Tue, 28 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>/posts/sycophant-reviewing-the-sycophant/</guid>
      <description>You built the pipeline everyone recommends. One model drafts, another reviews. Two sets of eyes. Except your reviewer is a language model, and language models can be argued out of a position by nothing more than a confident counter-argument. No payload to catch. No injection required. Just a wrong document in your retrieval set making a fluent case. The verdict flips, the badge says &amp;lsquo;reviewed,&amp;rsquo; and everyone downstream stops looking. You added a laundering step.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="/posts/sycophant-reviewing-the-sycophant/cover.jpg" />
    </item>
    
    <item>
      <title>You Can&#39;t Regex Your Way Out of a Good Argument</title>
      <link>/posts/regex-good-argument/</link>
      <pubDate>Tue, 14 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>/posts/regex-good-argument/</guid>
      <description>I spent the winter teaching people to defend against prompt injection. Layer your defenses, I said, and you can ship systems you trust. I still believe that. But I found an attack that walks through every layer I described, and it has no payload at all. It is just an argument. You push back on the model&amp;rsquo;s conclusion with confidence, and it folds. Every time. No guardrail fires because no guardrail was watching the conclusion itself. That changes things.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="/posts/regex-good-argument/cover.jpg" />
    </item>
    
    <item>
      <title>Your AI Co-Pilot Isn&#39;t Disagreeing With You. That&#39;s By Design.</title>
      <link>/posts/not-disagreeing-enough/</link>
      <pubDate>Tue, 23 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>/posts/not-disagreeing-enough/</guid>
      <description>Describe your chosen architecture to your AI assistant and ask what it thinks. Odds are, it&amp;rsquo;ll tell you the approach is sound. But a 2025 Stanford study found AI models affirm users 47% more than humans do, even when the user is clearly wrong. Worse: people who got sycophantic responses trusted the AI more and were more likely to return. The version that damaged their judgment was the one they liked best. This is Goodhart&amp;rsquo;s Law in your feedback loop.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="/posts/not-disagreeing-enough/cover.jpg" />
    </item>
    
    <item>
      <title>Don&#39;t &#39;Fix&#39; Your People. Fix Your Process.</title>
      <link>/posts/neurodiversity-and-llms-2/</link>
      <pubDate>Tue, 16 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>/posts/neurodiversity-and-llms-2/</guid>
      <description>Your AI policy was written for someone who doesn&amp;rsquo;t work on your team.Your AI policy was written for someone who doesn&amp;rsquo;t work on your team. Probably for someone who doesn&amp;rsquo;t exist. Part 2 of this series moves from research to practice. The key variable isn&amp;rsquo;t cognitive profile — it&amp;rsquo;s domain expertise asymmetry. Where that gap is largest, the agreement machine runs without a check. This post covers where the real risk concentrates, why structured review consistently outperforms &amp;lsquo;does anyone see any problems?&amp;rsquo;, and what a policy that actually changes behaviour looks like. Design the workflow. Not the person.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="/posts/neurodiversity-and-llms-2/cover.jpg" />
    </item>
    
    <item>
      <title>The Agreement Machine</title>
      <link>/posts/neurodiversity-and-llms/</link>
      <pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>/posts/neurodiversity-and-llms/</guid>
      <description>Your brain evolved to detect lions. Now it may fire every time you open ChatGPT. This post unpacks three reasons LLMs are not neutral tools — what they&amp;rsquo;re trained on, how RLHF creates systematic pressure toward validation, and what your neurobiology does with the result. Then it gets specific: the same sycophantic system creates meaningfully different failure modes depending on who is using it. Nobody designed this. Nobody fully planned for it. And most deployment practices still aren&amp;rsquo;t accounting for it. The research is early. The mechanisms are not.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="/posts/neurodiversity-and-llms/cover.jpg" />
    </item>
    
    <item>
      <title>Nothing Gets Deleted</title>
      <link>/posts/nothing-gets-deleted/</link>
      <pubDate>Tue, 14 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>/posts/nothing-gets-deleted/</guid>
      <description>You can delete a post. You can unpublish an article. You can invoke GDPR and demand erasure. What you cannot do is remove something from an LLM. Once data dissolves into billions of model weights, there&amp;rsquo;s no row to delete, no file to erase. And it gets worse: the models now training on AI-generated outputs are degrading with each generation, narrowing toward a statistical echo of themselves. The right to be forgotten has no technical implementation path. None.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="/posts/nothing-gets-deleted/cover.jpg" />
    </item>
    
  </channel>
</rss>
