<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>The Name on Bootstrapping.org</title>
    <link>https://bootstrapping.org/tags/the-name/</link>
    <description>Recent content in The Name on Bootstrapping.org</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://bootstrapping.org/tags/the-name/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why the Project Is Called Bootstrapping</title>
      <link>https://bootstrapping.org/why-the-project-is-called-bootstrapping/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://bootstrapping.org/why-the-project-is-called-bootstrapping/</guid>
      <description>&lt;p&gt;To bootstrap a computer is to take it from nothing to running: a tiny first program loads a bigger one, which loads the system. The word comes from the old joke about pulling yourself up by your own bootstraps, which you can&amp;rsquo;t do, and which a computer does every time it starts. In software it came to mean the first step that gets anything from empty to usable.&lt;/p&gt;&#xA;&lt;p&gt;An application has that step too. The migrations have run, the tables exist, and they&amp;rsquo;re empty. Before anyone can sign in, the roles need to be there. Before anyone can be invited, the permissions. Before anyone can pay, the plans. Putting those rows in place is the application&amp;rsquo;s bootstrap, and most projects have a seed script that does it once.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
