cognitive psychology. PhD 
A thoughtful post on the relationship between systems programming, low level programming, systems design, types, functional programming, and a few other things...https://twitter.com/wcrichton/status/1038925653880393728 …
-
In researching the post, it wasn't clear to me how applicable traditional systems thinking is to software design. After reading 1/2 of "Thinking in Systems", left the impression of being most useful for analyzing economies, ecosystems, etc. more than code.
Feels like software dev is more about how to break problems into subcomponents and define interfaces, while systems thinking is more about inputs/outputs and feedback loops. Then again, woefully ignorant on that kind of systems, so always looking for deeper connections!
-
-
A couple of people you might enjoy are Nancy Leveson, who's _Engineering a Safer World_ uses systems theory to study software safety, and Pamela Zave, who did a bunch of stuff on feature interaction in software.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
feedback is a neglected area of software design, although gradually as distributed systems grow more important it is being understood more. But its not yet a language level feature.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.