All posts in antifragile

TL;DR Every independently thinking person can easily recognize all the enterprise talks regarding "engagement", "motivation" & "ownership" as stinking pile of worthless, corporate rubbish. Neither knowledge nor creative workers can be so easily "tricked" (even if they can, in fact they're just fooling themselves short-term ...) for "higher engagement" - sustainable recipe for strong-performing, highly-effective organization has to be based on principles of everyone having (at least) "skin in the game": a win-win-win-... scenario with everyone proportionally participating in both risks & successes (shared definition!) of enterprise they…

TL;DR Concepts of fragility & antifragility apply to software engineering as well - but contrary to the common belief, fragility of the system is not related to the number of bugs or resilience (e.g. MTTR). It's far more about dichotomies between high inertia & high operational agility, openness for change & design brittleness, synchronous sequentiality & asynchronous monitoring - fragile systems (/ methods / tools) in building software tend to increasingly restrict, constrain & lengthen the development life-cycle, while ones that are not fragile preserve theirs "lightness", "leanness" & ease of use. This is the 2nd…

TL;DR Software systems, like all other kinds of systems, should be evaluated not only in terms of fitting their purpose & technical excellence. No system exists in a void, they are affected by time, local & global conditions, market fluctuations (not only in market related to system's core domain!) - one can't foresee (& shouldn't even try) everything that can happen, but it's crucial to NOT build systems in a way that makes them tightly coupled (stiffly dependent on) to current "snapshot of reality" (context of the moment) or predictions that don't have any factual justification (but…