Antifragility

From apppm
Revision as of 21:54, 18 September 2017 by Asger (Talk | contribs)

Jump to: navigation, search

Contents

Antifragility

The idea of antifragility is for a system to not only withstand or endure chaos, stress and high-impact events but to improve and upgrade itself. By looking at a system to be antifragile it adapts to the surroundings, and it is here that the antifragile system changes from the robust system. The robust system can withstand high-impacts and will not break when negative scenarios happen but neither will it take in the possitve impacts or scenarios, it will never improve before the whole system is changed. The antifragile system learns from the impacts, negative and possitive, and thus becomes stronger with each hit it takes.


The concept of antifragility is developed by Nassim Nicholas Taleb and discussed in his books, Fooled by Randomness, The Black Swan and Antifragility.



Antifragility as a concept

something that is robust merely tolerates adverse or unexpected conditions, whereas something that is antifragile thrives—its performance actually improves. - Robert W. Lucky, Antifragile Systems

The antonym of “fragile” is not robustness or resilience, but “please mishandle” or “please handle carelessly,” using an example from Taleb when referring to sending a package full of glasses by post. - Terje Aven, The Concept of Antifragility and its Implications for the Practice of Risk Analysis


How to define an antifragile system?

- When do you reach an antifragile system? - What is the rules/guidelines for the anitfragile system? - Can an antifragile system become (anti)antifragile? And what is it then?


The use of antifragility

- What use would the antifragile system give? - Is there any benefits that does not exist today?

- Is there places that the antifragile system cannot be used?


Antifragility vs robustness/resilient

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox