Speed of change in your system or software, and how you deal with the friction of that predictable, or even unpredictable, change is critical to understanding just how antifragile your software needs to be.
Antifragility begins with understanding how to compose your software along the lines of change, grouping things together that change together, and that is the purpose of the Life Preserver*.
* To feature most heavily in a later post, and of course in the book linked to below.
For more information on Antifragility generally, the canonical book by Nassim Nicholas Taleb is the place to start.
For more on Antifragility in Software, that's what my book is all about and I expect to have a complete draft ready this week. If you can spare 3 days in London to learn about how to develop and evolve software faster than the competition, then my course at Skills Matter would be time well spent.
For help adopting antifragility in your own software, contact my team at Simplicity Itself.