
Describes a highly productive approach to application development based on "Flow-Based Programming" (FBP), a programming paradigm that has been used sporadically for over 20 years. Most commonly used paradigms focus on generating novel programming code for a given application. FBP focuses on modularizing tasks so they can be fit together and be reused in an infinite variety of ways, yielding a kind of recyclable programming code. Annotation copyright by Book News, Inc., Portland, OR
Of course, in recent times, it has become all that much more relevant to me as I began working in data science/engineering space. Even though it's not specifically about code structure for a particular language, it addresses a common flaw in most programming approaches that seem to treat all functionality as a servant of the current context which is strange and silly and not how anything works in physical information processing so why do it in code?
A somewhat common pattern that maps well to FBP is "Railway Oriented Programming." Though FBP in full takes this well beyond simply shooting errors along in sideband to the happy path.
Also, if looking for glue, check out Wikipedia's list of programming paradigms or types of programming languages. Quite a few including some styles you may have not heard of.
I'm pretty surprised I haven't seen J. Paul Morrison's "Flow-Based Programming" mentioned anywhere in the post or these comments. I first read this book years ago as a undergrad and it made a big impact on me. It discusses ideas very similar to the ones proposed for Glow. You can read it free online here:
http://www.jpaulmorrison.com/fbp/
You can find links to several existing implementations of flow-based programming on Wikipedia:
Regardless of syntax this is a very interesting language design space, since it seems to hold some of the most promise for lowering average software complexity.