<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Open Source on Joel Merrick</title>
    <link>https://www.joelmerrick.co.uk/tags/open-source/</link>
    <description>Recent content in Open Source on Joel Merrick</description>
    <generator>Hugo</generator>
    <language>en-GB</language>
    <lastBuildDate>Mon, 19 Oct 2026 22:00:00 +0100</lastBuildDate>
    <atom:link href="https://www.joelmerrick.co.uk/tags/open-source/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Dummy Run: letting fictional users try your app first</title>
      <link>https://www.joelmerrick.co.uk/blog/dummy-run/</link>
      <pubDate>Mon, 19 Oct 2026 22:00:00 +0100</pubDate>
      <guid>https://www.joelmerrick.co.uk/blog/dummy-run/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://dummyrun.dev&#34;&gt;Dummy Run&lt;/a&gt; is an open-source tool that lets AI act as your users and try your application before your customers do. It is available on &lt;a href=&#34;https://github.com/dummy-run/dummy-run&#34;&gt;GitHub&lt;/a&gt; under the Apache 2.0 licence. The name is British English for a trial run; here, the dummies do the running.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-problem&#34;&gt;The problem &lt;a class=&#34;heading-anchor&#34; href=&#34;#the-problem&#34; aria-label=&#34;Link to this section&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Most teams now build a preview environment for every pull request. In principle, someone checks each preview before it is merged. In practice, that check is often brief, it follows the expected path, and it is done from a single account. Few people test as a user with restricted permissions, a different device or an unusual way of working, which is where many real problems appear.&lt;/p&gt;</description>
    </item>
    <item>
      <title>My Code in the Arctic</title>
      <link>https://www.joelmerrick.co.uk/blog/github-arctic-vault/</link>
      <pubDate>Fri, 13 Jun 2025 15:00:00 +0100</pubDate>
      <guid>https://www.joelmerrick.co.uk/blog/github-arctic-vault/</guid>
      <description>&lt;figure class=&#34;figure&#34;&gt;&lt;img class=&#34;ttpic&#34; src=&#34;https://www.joelmerrick.co.uk/images/blog/github-arctic-vault_hu_21c62f3f2cad691b.png&#34; alt=&#34;GitHub Arctic Code Vault&#34; width=&#34;140&#34; height=&#34;140&#34; loading=&#34;lazy&#34; decoding=&#34;async&#34;&gt;&lt;/figure&gt;&lt;p&gt;I never thought my code would end up buried in the Arctic ice, preserved for a thousand years. But that&amp;rsquo;s exactly what happened when GitHub archived my open source contributions as part of their &lt;a href=&#34;https://archiveprogram.github.com/&#34;&gt;Arctic Code Vault&lt;/a&gt; project.&lt;/p&gt;&#xA;&lt;h2 id=&#34;my-code-frozen-in-time&#34;&gt;My code, frozen in time &lt;a class=&#34;heading-anchor&#34; href=&#34;#my-code-frozen-in-time&#34; aria-label=&#34;Link to this section&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;On February 2, 2020 (02/02/2020), GitHub captured a snapshot of all active public repositories and preserved that data in the Arctic Code Vault. The snapshot included:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
