<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>explainer on Aftermarket.dev</title>
    <link>https://aftermarket.dev/tags/explainer/</link>
    <description>Recent content in explainer on Aftermarket.dev</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 19 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aftermarket.dev/tags/explainer/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What a Software Aftermarket Is and Why You Already Use One</title>
      <link>https://aftermarket.dev/what-a-software-aftermarket-is-and-why-you-already-use-one/</link>
      <pubDate>Mon, 19 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/what-a-software-aftermarket-is-and-why-you-already-use-one/</guid>
      <description>Every developer has fixed software they didn&amp;rsquo;t write. Most of us just don&amp;rsquo;t call it that.
You put nginx in front of an old app to add a header it forgot. You wrote a shim so a client from 2017 could keep talking to a rewritten API. You patched a vendor&amp;rsquo;s config file, watched the next upgrade wipe your change, and patched it again. Somebody on your team keeps a script that &amp;ldquo;fixes the export&amp;rdquo; every Monday morning.</description>
    </item>
    
  </channel>
</rss>
