Week 35, year 2013

• Antifragile - Things That Gain from Disorder - What is the opposite of fragile (breaks when confronted with unexpected events)? Changes are people answer with robustness (stays the same under unexpected events). But there’s another way to look at it. Fragile Robust Antifragile Best case scenario Remains unchanged Remains unchanged Improves Worst case scenario Breaks Remains unchanged Remains unchanged Taleb introduces the term antifragile for systems that don’t simply stay the same when subjected to stressors, volatility, and exceptions, but that actually change for the better. Wildfire We tend to naively intervene in systems, without taking into account their natural antifragility. Take wildfire. If we attempt to stabilize - that is, prevent wildfires from happening - we believe we make the forest more robust. [Mathias Verraes]
• Facilitating Event Storming - Event Storming is a technique where you get the developers and the business stakeholders in a room, and visualize the business processes. You do this using stickies with domain events and causality (such as commands), and end with drawing boundaries for aggregates, bounded contexts and subdomains. It’s developed by Alberto Brandolini and is deeply rooted in Domain Driven Design, and CQRS/ES. I facilitated an Event Storming session with the team of Qandidate. com in Rotterdam. I’ve read an early draft of Alberto’s paper on Event Storming, that inspired most of what I did. [Mathias Verraes]

Permalink | From 26 August 2013 to 01 September 2013 | Last updated on: Mon, 7 Jun 2021 09:18:52 GMT