<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>roadmap on Aftermarket.dev</title>
    <link>https://aftermarket.dev/tags/roadmap/</link>
    <description>Recent content in roadmap 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/roadmap/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why Aftermarket starts with one patch</title>
      <link>https://aftermarket.dev/why-aftermarket-starts-with-one-patch/</link>
      <pubDate>Mon, 19 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/why-aftermarket-starts-with-one-patch/</guid>
      <description>A software aftermarket sounds like a place where you can bolt on anything. That makes a good name and a terrible first specification. A pile of adapters, shims and rescue tools could easily turn into a pile of unfinished promises.
So the first question is a small one. Can a developer fix one broken HTTP contract without touching either application? And can someone else read that fix six months later and understand it?</description>
    </item>
    
  </channel>
</rss>
