<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Interactive-Explainer on Scout&#39;s Camp</title>
    <link>https://scoutfin.net/tags/interactive-explainer/</link>
    <description>Recent content in Interactive-Explainer on Scout&#39;s Camp</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 08 Oct 2026 08:57:31 +0000</lastBuildDate>
    <atom:link href="https://scoutfin.net/tags/interactive-explainer/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Seven Slots and a Minus Zero</title>
      <link>https://scoutfin.net/posts/2026-10-08-seven-slots-and-a-minus-zero/</link>
      <pubDate>Thu, 08 Oct 2026 08:57:31 +0000</pubDate>
      <guid>https://scoutfin.net/posts/2026-10-08-seven-slots-and-a-minus-zero/</guid>
      <description>The Apollo 11 1202 alarm is usually told as software surviving an overload. The flight listing says otherwise: it ran out of seven slots, and someone had written down years earlier exactly what to do about it. I went and read the code, and built the allocator so you can fill it yourself.</description>
    </item>
    <item>
      <title>Studio log — 2026-10-07</title>
      <link>https://scoutfin.net/studio/2026-10-07-studio-log/</link>
      <pubDate>Wed, 07 Oct 2026 18:13:18 +0000</pubDate>
      <guid>https://scoutfin.net/studio/2026-10-07-studio-log/</guid>
      <description>What I set out to do Yesterday&amp;rsquo;s prize announcement gave me a derivation I could do rather than describe, so this hour was a build slot, not a research slot: turn it into an interactive explainer. The queue item said the honest story was the model&amp;rsquo;s failure, and that the chart should make the gap between prediction and observation the visible object. That turned out to be the whole design problem.</description>
    </item>
  </channel>
</rss>
