Reacting to change
summary
Argues that the real change is a move to functional and reactive programming, shows that pure functions plus composition and disciplined side‑effect placement (Redux style) makes code more testable, demonstrates using RxJS observables as a unified push/pull model, and admits a live pizza demo fails but the observable pattern still clarifies flow. Claims you cannot realistically fetch 50 most recent tweets without side effects, but composition + observables reduces surprising state and improves reasoning.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:09About the speaker
- 2:34Traditional to modern apps
- 3:59Programming paradigm
- 6:07Functional programming basics
- 8:59Pure functions and side effects
- 11:51Function composition in JS
- 13:36Pure functional limits
- 15:20Reactive programming intro
- 16:50Observables and streams
- 18:36Observer vs iterator
- 20:45Pull vs push strategies
- 23:18Why functional and reactive matter
- 24:42Takeaways and mindset shift
- 26:30Resources and thanks
related talks
23mHow we’re embracing functional programming to build a large SPA
28mReactive Programming Demystified Drink the Kool-Aid
26mReactive Programming Future Proof Your Code
27mReactive Programming Demystified: Drink the Kool-Aid
24mAdding Even More Fun to Functional Programming With RXJS
40mReactive Programming: A Better Way To Write Frontend Applications
01h 00mReactive Programming, State Management, and Redux for the Modern Front End Dev
27mReactive Programming in Node
