Reactive Programming Metaphor
Updated 2026-08-15
INTRODUCTION
English translation pending.
CORE DEFINITION
Reactive programming is a paradigm built on data streams and the propagation of change, in which a component declares what it depends on and is updated automatically when that dependency changes, instead of pulling the data on a schedule. As a personal management model it argues against polling, such as checking email every few minutes, and for a mechanism with thresholds that releases attention until an event actually occurs. The key qualification is that the wiring must be designed in advance, and overuse makes the flows impossible to trace.
SCAFFOLDING EFFECT
Reduce cognitive load
- Use dependency declaration: list which signals you actually need and drop the rest. - Use threshold setting: define the level at which an event is worth your attention. - Use push handoff: let a filter notify you instead of checking the source yourself.
Anchor fast decisions
Polling spends attention on the gap between checks, whether or not anything has changed, which is why the cost is constant and the yield is intermittent. A declared dependency with a threshold inverts the ratio, since attention is claimed only when the condition crosses. The wiring carries the cost once, at design time, and the filter then runs cheaply in the background for as long as it is needed.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Responsive_web_designverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS