4 ms·
Leverage Points: Places to Intervene in a System (1999)
- Jtsummers 1y agohttps://news.ycombinator.com/item?id=17764576 https://news.ycombinator.com/item?id=17764576 - August 2018, 12 comments https://news.ycombinator.com/item?id=13959999 https://news.ycombinator.com/item?id=13959999 - March 2017, 11 comments
- treetalker 1y agoRelated rules of thumb, from the conclusion of James C. Scott's Seeing Like a State (pages 344–45 in my version): - Plan on surprises. - Plan on human inventiveness. - Favor reversibility. - Take small steps; stand back; and observe before doing more. Buffer, optionality, advantageous smallness, and bricolage are our watchwords. "It is impossible to legislate for the future." —Prince Peter Kropotkin "The first rule of intelligent tinkering is to keep all the parts." —Aldo Leopold --- See also Gall's Law.
- asplake 1y ago- Act always to increase options - von Foerster - Act always to increase possibility - Nora Bateson
- esafak 1y agohttps://en.wikipedia.org/wiki/Twelve_leverage_points https://en.wikipedia.org/wiki/Twelve_leverage_points
- tenuousemphasis 1y agoFYI this is one of the authors of The Limits to Growth.
- entropyie 1y agoExcellent piece, captivating. I found many parallels here to managing IT. So much of control theory and systems engineering is relevant to developing and deploying cloud systems, improving performance etc... Many times I've seen engineers polishing and optimizing the code of an existing system without ever questioning the process itself or indeed the paradigm. I myself was in that position, spent 5 years optimizing the parameters of a complex system, only to realize that system was put in place based on faulty assumptions that were never questioned. The whole thing could have been removed and performance sped up 200%.