Why I bet my business on React
summary
Claims that betting the business on React gives measurably faster iteration and fewer bugs, using a stack of Node + GraphQL + React to build Seat, a meetup-organizer product. Demonstrates tooling that actually ships: Create React App → Next.js for SSR, Material‑UI and react‑select for reusable bits, and a react-sketchapp demo worked to sync design and code. Results: smaller, componentized codebase, easier onboarding, and shipping features faster than rebuilding UI from scratch.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 2:40HTML
- 4:05Web
- 8:50Framework fatigue
- 10:43React components
- 13:18Design systems
- 17:13Code as the source
- 23:07React Patterns
- 23:47JSX
- 24:57Multiple components
- 26:57Single responsibility principle
- 28:02Children child components
- 33:52Getting started with React
- 34:47Gubbi
- 36:02Create Next
- 38:51React vs External Design Systems
- 41:43Creating a React App
- 43:30Preact vs React
- 45:45React Stack
- 46:29React Native
