Going beyond Redux. Diversify frontend state management
summary
Claims that Redux is the default hammer get tested against concrete practices: document the domain model, ship tiny POC apps that mimic the stack, and include learning links in PRs. Evidence includes tool substitutions — statecharts, Bacon.js, Overmind used on a real project — and a measurable test: more than 30 comments on a first PR signals a documentation failure. Advice: try specific alternatives, record why they were chosen, and verify they actually reduce onboarding friction.
AI-written summary · about
chapters (26)
- 0:00Intro
- 1:00Documentation
- 1:55State management
- 2:25Google Trends
- 3:12How we tried
- 3:34What can be done about it
- 4:33How many options we have
- 5:26Whats the deal
- 6:55Fear of being judged
- 7:45Solutions
- 11:10Leave a presentation about Redux
- 11:21Believe in what you preach
- 11:37Diversify frontend state management
- 12:22Context is key
- 12:46PR reviews
- 13:05Bridge the gap
- 13:46Asking more questions
- 14:07Frozen
- 14:19DVD
- 15:05Domain Driven Design
- 16:18Do you have kids
- 17:35Have the other end
- 18:12Testing
- 18:57Support
- 19:55Create from scratch
- 20:39Ride the documentation
related talks
30mMake React State-Management great again
51mBuilding React Applications with Redux
28mThe State of React State in 2019
41mThe Battle of State Management in modern frontend applications
18mDestructuring state management (in React)
15mRedux is dead, long live redux!
35mNavigating the Hype Driven Frontend Development World
01h 00mReactive Programming, State Management, and Redux for the Modern Front End Dev