<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>StackBench</title>
    <link>https://stackbench.dev</link>
    <description>A developer&apos;s notebook on second brains, AI agents, and build-in-public. Sometimes the writing finds a shape and becomes a thing you can buy. StackMind was the first.</description>
    <language>en-us</language>
    <lastBuildDate>Thu, 09 Apr 2026 23:33:19 GMT</lastBuildDate>
    <atom:link href="https://stackbench.dev/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to build a developer knowledge base that actually works</title>
      <link>https://stackbench.dev/writing/how-to-build-a-developer-knowledge-base-that-actually-works</link>
      <guid isPermaLink="true">https://stackbench.dev/writing/how-to-build-a-developer-knowledge-base-that-actually-works</guid>
      <pubDate>Thu, 09 Apr 2026 00:00:00 GMT</pubDate>
      <description>Most developer note systems fail because they&apos;re organized by when you wrote something, not by when you&apos;ll need it. Here&apos;s how to build one that compounds.</description>
    </item>
    <item>
      <title>The notes a developer keeps so the work compounds</title>
      <link>https://stackbench.dev/writing/the-notes-a-developer-keeps</link>
      <guid isPermaLink="true">https://stackbench.dev/writing/the-notes-a-developer-keeps</guid>
      <pubDate>Tue, 07 Apr 2026 00:00:00 GMT</pubDate>
      <description>On knowledge that builds on itself, why most of yours doesn&apos;t, and what changes when it does.</description>
    </item>
  </channel>
</rss>
