<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Git Good on PärPod</title>
    <link>https://parpod.net/series/git-good/</link>
    <description>Recent content in Git Good on PärPod</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 21 Feb 2026 00:00:00 +0100</lastBuildDate>
    <atom:link href="https://parpod.net/series/git-good/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The AI That Cleaned My Repos</title>
      <link>https://parpod.net/episodes/ai-that-cleaned-my-repos/</link>
      <pubDate>Sat, 21 Feb 2026 00:00:00 +0100</pubDate>
      <guid>https://parpod.net/episodes/ai-that-cleaned-my-repos/</guid>
      <description>&lt;h2 id=&#34;thirty-two-repos-and-a-confession&#34;&gt;Thirty-Two Repos and a Confession&lt;/h2&gt;&#xA;&lt;p&gt;On a Tuesday morning in February two thousand twenty-six, a developer in Jämtland, Sweden, asked an AI to review his Git setup. Not a large company. Not a team of fifty. One person, working from a house in a village called Kall, population somewhere south of three hundred, running about thirty personal projects across a VPS in Paris, a Raspberry Pi in his living room, and a MacBook on his kitchen table.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Copy-Paste Catastrophe</title>
      <link>https://parpod.net/episodes/copy-paste-catastrophe/</link>
      <pubDate>Sat, 21 Feb 2026 00:00:00 +0100</pubDate>
      <guid>https://parpod.net/episodes/copy-paste-catastrophe/</guid>
      <description>&lt;h2 id=&#34;the-folder-of-shame&#34;&gt;The Folder of Shame&lt;/h2&gt;&#xA;&lt;p&gt;You know that moment when you are working on something important and you think &amp;ldquo;I should probably save a version of this before I break everything&amp;rdquo;? So you do what every reasonable person does. You save a copy. Project final dot doc.&lt;/p&gt;&#xA;&lt;p&gt;But then you realize you need to make another change. So you save another copy. Project final version two. And then your colleague sends you edits. Project final version two, John&amp;rsquo;s edits. And you merge those in but want to keep the old version just in case. Project final version three with John&amp;rsquo;s stuff.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Education Problem</title>
      <link>https://parpod.net/episodes/education-problem/</link>
      <pubDate>Sat, 21 Feb 2026 00:00:00 +0100</pubDate>
      <guid>https://parpod.net/episodes/education-problem/</guid>
      <description>&lt;h2 id=&#34;the-most-viewed-question-on-the-internet&#34;&gt;The Most Viewed Question on the Internet&lt;/h2&gt;&#xA;&lt;p&gt;The last series ended with Git having won. The format wars, the competing tools, the years of skepticism — all resolved in Git&amp;rsquo;s favor. What we did not look at is what winning actually looks like from inside the industry, for the millions of developers who now wake up every morning and have to use the thing.&lt;/p&gt;&#xA;&lt;p&gt;Somewhere right now, a developer is panicking. They just committed something they should not have committed, or committed to the wrong branch, or pushed a change that broke everything, and they are doing what every developer in this situation does. They are opening a browser and typing &amp;ldquo;how do I undo&amp;rdquo; into a search bar.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Linux Kernel Crisis of 2005</title>
      <link>https://parpod.net/episodes/linux-kernel-crisis/</link>
      <pubDate>Sat, 21 Feb 2026 00:00:00 +0100</pubDate>
      <guid>https://parpod.net/episodes/linux-kernel-crisis/</guid>
      <description>&lt;h2 id=&#34;patches-by-email&#34;&gt;Patches by Email&lt;/h2&gt;&#xA;&lt;p&gt;On a Tuesday in late March, two thousand five, a kernel developer named Andrew Morton sat down at his desk and began doing what he did every single day. He opened his email client and started reading patches. Not five patches. Not fifty. Hundreds of them. Plain text diffs, the raw language of code changes, flowing into his inbox from developers on six continents. Each one a small proposal for how the Linux kernel should be different tomorrow than it is today. Morton would read the patch, decide if it made sense, test it against his own copy of the kernel source tree, and either apply it or write back with questions. Then he would move on to the next one. And the next one. And the next one. Every single day.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Trust and the Supply Chain</title>
      <link>https://parpod.net/episodes/trust-and-the-supply-chain/</link>
      <pubDate>Sat, 21 Feb 2026 00:00:00 +0100</pubDate>
      <guid>https://parpod.net/episodes/trust-and-the-supply-chain/</guid>
      <description>&lt;h2 id=&#34;half-a-second-too-slow&#34;&gt;Half a Second Too Slow&lt;/h2&gt;&#xA;&lt;p&gt;On a Friday evening in late March two thousand twenty-four, a software engineer named Andres Freund was running benchmarks on his PostgreSQL database. Freund worked at Microsoft, but his real passion was PostgreSQL, the open source database he had been contributing to for over a decade. He was testing on a machine running Debian Sid, the bleeding-edge development version of Debian Linux, and he noticed something strange. His SSH logins were taking about half a second longer than they should.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
