Back to React: The Story of Two Apps
summary
A concrete before-and-after: an early app embeds React + Rails stack as a focused “missing piece,” uses inline styles, larger components and just-in-time extraction, and runs for three years with almost no maintenance complaints; a later app piles on Redux Router Flux and many tiny libraries, cycles through three Flux versions and becomes brittle. Practical rules follow — five liberating constraints (who drives the app, optimize for change, know component shapes, avoid bleeding edges, partner don’t depend) — plus examples of tools and where they actually helped or hurt.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:425 WAYS TO BE A HAPPY REACT DEVELOPER
- 5:47REACT IS A GOOD MISSING PIECE
- 10:23MAINTAINABILITY
- 10:36NOBODY ASKS ME ABOUT IT
- 13:22CLARIFYING DESIRED PRACTICES
- 16:10FIVE LIBERATING CONSTRAINTS
- 19:03WHAT ROLE DOES REACT PLAY IN YOUR APP?
- 19:50OPTIMIZE FOR CHANGE
- 24:38CHOOSE TOOLS YOU CAN MASTER
- 26:54GUARD OUR STACK
- 27:23KNOW WHO'S DRIVING
