Antifragile Designing the Systems of the Future - Barry O'Reilly - DDD Europe 2019

Domain-Driven Design Europe 2019
dddeurope.com / ddd_eu
Organised by Aardling (aardling.eu/)
Antifragile - Designing the Systems of the Future
Based loosely on the book ‘Anti-fragile’ by Nicholas Nassim Taleb, we look at how his theories on fragility and the ability to withstand shocks can be interpreted to help us design, produce, and manage better systems that can help us deal not only with failures, but also with rapidly changing markets and expectations in modern software development. We look at how we can combine Complexity Science and Systems Engineering to produce solutions that can both respond to change and provide quality.
Biography
Barry is a CITA-P certified Architect who has held Chief Architect positions at Microsoft and and iDesign. He has also been a startup CTO, the Worldwide Lead for the Solutions Architecture Community at Microsoft, and founder of the Swedish Azure User Group. He is also a trainer for IASA.

[@HubertSven]

First approach I personally heard of that addresses the "intuition of software architects" and "complex vs. complicated software systems" in a coherent and presumably practical way.

[@leeroyescu]

Thanks for this! Been muddling around the concept of *stressors* for so long. I don't care about the particulars of a solution when starting something. I want to hear bitching, operationalized. The problems, the main enemies, what domain experts crack jokes about because it's so present in their daily experience. Because of the horrible bias against negativity and pablums like "don't come to me with problems, come with solutions" running rampant in culture we fail to recognize that _knowledge grows by subtraction much more than by addition (via negativa)._ The most valuable overview of a topic I can imagine is the slice of the evolutionary fitness landscape, where mild stressors put up hills, severe stressors put up cliff faces, paths of least resistance wind in the valley, and gaps between obstacles reveal promising untapped niches. Not what is, what could be. Cultivate ways to be less dynamically challenged.

anti-fragile systems seem to have 4 properties in common: modularity, weak links, redundancy, “diversity among modules”. if you want to know how to achieve that watch the video

[@nelmezzodelcamminooo]

encapsulation, decoupling, "diversity among modules" is still encapsulation, redundancy is about operations and infrastructure more than about design by itself