Bar none, the most common question was "what's the benefit?". The answer is "there are lots", but this post will introduce the main one.
Antifragility takes effort to implement and so there had better be a benefit for that cost, right? Absolutely. The first big payback for designing your software with antifragility in mind (notice that this is NOT 'robust' software, nor 'fragile' software; this is software that thrives on change) is in the fact that antifragility helps you embrace change. The secret is in the subtitle of the key book on Antifragility, "Things that gain from disorder".
Projects, products and needs are unpredictable, that was why we originally got into agile software development in the first place. Antifragility is a key property of your software if it too is going to be able to keep pace with emerging needs placed upon it, and not end up being the 'elephant in the standup' (more on the elephant in a forthcoming post).
So if you want to build software that embraces change and gives you an edge when aiming to be faster to market than your competitors (or just to impress the boss with your speed), antifragility is going to be something you want to design in.
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.
More posts coming soon based on the wonderful questions I received from the twitterati!