Why We’re Afraid of Change
summary
Version numbers lie: a patch like Swift 4.0.1 → 4.2 and a minor like Facebook Android SDK 4.0 → 4.27 both break real apps, forcing a binary search to 4.10.1. Propose registry checks that verify public API and types like Elm does, run previous version’s tests or dependent tests before publish, and attach codemods guaranteed safe to upgrades so installs can apply them automatically. Use opaque types to avoid future breakage and publish a reason-publish index that enforces these rules.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:02Current State of Dependencies
- 7:29Author Centric
- 10:08Indicating Breaking Changes
- 10:51Dependency Changes
- 21:22Opaque Types To Reduce the Number of Breaking Changes
- 23:19Code Mods
related talks
30mBreaking backwards compatibility: The easy way!
15mHow Apps Are Actually Built
01h 00mVersioning 1.0.1
23mA Pattern for a Well-Knit JavaScript Project
01h 01mGuide to Destroying Codebases the Demise of Clever Code
22mFear of the computer
23mUntangling Your Dependencies: A Pattern for a Well-Knit JavaScript Project
32mHow to successfully shift from app development to SDK development