For those with technical interests, there are at least 2 more technical versions of this that I know of. The first is the Bode waterbed effect: improving performance in one part of the range of a control system worsens it in another part https://ocw.mit.edu/courses/electrical-engineering-and-computer-science/6-245-multivariable-control-systems-spring-2004/lecture-notes/lec5_6245_2004.pdf …
-
-
Show this thread
-
Computer science and design people seem to have a less technical waterbed theory formulation https://en.wikipedia.org/wiki/Waterbed_theory …
Show this thread -
Wrote about this stuff in a 2012 post that I probably need to revisit andhttps://www.ribbonfarm.com/2012/04/18/hacking-the-non-disposable-planet/ …
Show this thread
End of conversation
New conversation -
-
-
I define it as a causality loop - cyclical nature of system means root cause analysis takes you back to your starting point. To “fix” such a system you need to encircle it, hence simultaneously fix bug at each cause in the cycle.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Extremely good, I’m shocked I’ve never heard this articulated in a tweet
-
I’ve seen simpler versions like “you hurt when you try to help”, taleb’s iatrogenics- system is too complex for simple-minded “fixing” - but “fixing one bug makes another” feels truthier & more nuanced on some dimension. In the “you can only choose where you want your bugs” sense
- Show replies
New conversation -
-
-
I’m down as long as we maintain a clear distinction between • complicated systems • complex systems
-
I refuse!
- Show replies
New conversation -
-
-
What if every fix introduces slightly more than 1 new bug on average? Is there a way to stop the runaway trend without burning it to the ground & starting over?
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.