For large-scale software systems, Van Roy believes we need to embrace a self-sufficient style of system design in which systems become self-configuring, healing, adapting, etc.. The system has components as first class entities (specified by closures), that can be manipulated through higher-order programming. Components communicate through message-passing. Named state and transactions support system configuration and maintenance. On top of this, the system itself should be designed as a set of interlocking feedback loops. Here I’m reminded of systems thinking and causal loop diagrams. These connect several of my systems design principles
Programming paradigms for dummies: what every programmer should know
from Adrian Colyer
Filed under:
Same Source
Related Notes
- In Eliyahu M. Goldratt's "Theory of Constraints", you...from ycombinator.com
- This reminds me of the story where a Houston airport kept getting c...from ycombinator.com
- Dependencies (coupling) is an important concern to address, but it&...from kbouck
- Deep and shallow modules: The best modules are deep: they allow a ...from John Ousterhout
- By replacing integration tests with unit tests, we're losing al...from Computer Things
- I propose that there is one problem chief among them, an impetus fo...from George Hosu
- When software -- or idea-ware for that matter -- fails to be access...from gist.github.com
- Any software is considered free software so long as it upholds the ...from writefreesoftware.org