Please enable JavaScript.
Coggle requires JavaScript to display documents.
Proposal for an Antifragile Software Manifesto (3: Suggested principles…
Proposal for an Antifragile Software Manifesto
Introduction
Antifragility is stronger than resilience or
robustness. The resilient entity resists shocks and stays the same; the antifragile entity gets better
NASA adopting: new antifragile software architecture to “address future challenges [...] since it is not simply to do what we
know how to do now better: we need to do things we currently do not know how to do”
2: Why a manifesto
Proposed principles just suggestions to start the discussion
Extreme Agile
Agile thinking essential to build antifragile organization
Antifragility goal: learn from errors to become stronger. Agile goal: build in an efficient and effective way.
3: Suggested principles
P1: Our highest priority is to satisfy the customer by building a non-linear, proactive, and self adaptive system
P. 2 – We welcome changing scenarios where unexpected events (Black Swans) are the real paradigm shifting
entities
P3: We deliver assuring embedded and adaptive fault tolerance
This one seems questionable. How is this different than robustness? Not made better or worse by stress, just staying the same? Or is adaptive more meaningful in that the system adapts as a result of these faults?
P. 4 – All stakeholders, and the broader environment, lead the antifragile organization
P. 5 – Build antifragile projects around motivated, skilled and open minded people. Give them the environment
and support they need, and trust them to get the job done
P. 6 – The most efficient and effective method of building an antifragile organization is building on honest, open
and transparent communication
P. 7 – Continuous exposure to faults and automatic fixing is the primary measure
P. 8 – An antifragile organization promotes a context aware environment. The stakeholders should be able to
maintain a system indefinitely
P. 9 – Continuous attention to technical excellence, reality, redundancy
P. 10 – Error loving - the art of learning to be antifragile – is essential
A antifragile system should not block itself in front of unknown inputs, it has to
accept them and to use machine learning algorithms to improve its efficiency.
P. 11 – Antifragile architectures emerge from self – organizing, context aware teams
P. 12 – At regular intervals, the developing team reflects about the context situation, on how to become more
effective, then tunes and adjusts its behavior accordingly