Archive
2026
- How AfterBridge Was Tested
- Case Study: Serving Nightly CSV Exports and a SQLite Inventory as a JSON API
- AfterBridge Released to Serve Old CSV Exports and SQLite Files as a JSON API
- How TOML Support in AfterConfig Was Tested
- How AfterSchema Was Tested
- How AfterHook Was Tested to Turn Every Change Into One Event
- How AfterGuard Was Tested to Let Nothing Ambiguous Through
- How AfterConfig Was Tested to Never Write a Vendor Config File
- Case Study: Putting an Old Admin Panel Behind AfterGuard
- Case Study: Keeping Old Shop Reports Working After a Schema Change
- Case Study: Keeping Changes to a Vendor TOML Config Through an Upgrade
- Case Study: Getting Webhooks From an Old App With AfterHook
- Case Study: Getting Through a Vendor Upgrade With AfterConfig Guards
- AfterSchema Released to Keep Old SQL Working After a Schema Change
- Aftermarket Hardens Patch, Adapt and Record Against Stalled and Cut Off Uploads
- Aftermarket Fixes Proxy Answers Cut Off Under Load
- AfterHook Released to Send Webhooks From Software That Never Had Any
- AfterGuard Released to Put a Lock on Old Apps That Have None
- AfterConfig Released to Change Vendor Config Files Without Editing Them
- AfterConfig Adds TOML Overlays That Keep Every Comment
- How AfterTest and AfterDiff Were Tested With Secrets in Every Request
- How AfterAPI Was Tested Against an Old Client Test Suite
- Case Study: Moving an Old Client to a New Customer API With AfterAPI
- Case Study: Fixing a Moved Exchange Rate Endpoint With Two AfterPatch Rules
- Case Study: Catching a Renamed Field Before Release With AfterTest and AfterDiff
- AfterTest and AfterDiff Released to Record Traffic and Compare Versions
- AfterAPI Released to Keep Old API Clients Working
- Why Aftermarket starts with one patch
- Why Aftermarket Is Named After Car Parts
- What a Software Aftermarket Is and Why You Already Use One
- How AfterPatch Was Tested Before Its First Release
- AfterPatch Released as the First Aftermarket Tool