When you are fragile, you depend on things following the exact planned course, with as little deviation as possible—for deviations are more harmful than helpful. This is why the fragile needs to be very predictive in its approach, and, conversely, predictive systems cause fragility. When you want deviations, and you don’t care about the possible dispersion of outcomes that the future can bring, since most will be helpful, you are antifragile.
I wish the author would have also interviewed some software people , heh, this aligns with the agile versus the waterfall way of building software
