[norswap]

I was kind of hoping for a document that outlined principles to make the engineering process truly antifragile, i.e. one that would thrive under contingencies.

Honestly, I have trouble fathoming how such a thing would be even possible in the realm of software. Maybe a system that "learns" previous failures and proactively monitor failure conditions / throttles contended ressources? (Seems quite specific already)

And the document surely didn't tell me.

[colbyh]

I actually think the former would be more within in the spirit of Taleb's book. software is the result of a complex, sometimes problematic process and not every piece of software needs to be antifragile. when bugs or system outages pop up it isn't the responsibility of the software to fix itself, it's the responsibility of the team behind it.