How to Stay Tech Relevant
summary
Claims that principles beat tool churn by showing concrete work: writes a small compose function and reuses it with React hooks, demos it composing UI behavior, and logs live outputs; benchmarks show Gatsby 1 supports ~2,500 pages but requirements jump from 2,000 to 10,000 pages; rather than rewrite, composes a create-react-app + SSR hack (extra server box), publishes an NPM package that powers a Boston University site — it runs but the project overruns budget and the client is unhappy.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:42Alex Lobera
- 1:14JavaScript fatigue
- 2:05Table of content
- 2:51My real world story
- 3:34What do you do good things
- 4:54How to fix a problem
- 5:54Physical principle
- 6:56Learning Principles
- 7:27Demo
- 14:32Client Story
- 15:15Gatsby
- 16:30ServerSide Rendering
- 20:40NPM
- 21:19Summary
related talks
34mNavigating the Hype-Driven Frontend Development World Without Going Insane
26mBuilding modern React applications
32mThe Modern Way of Making Websites in React
49mScalable Best Practices for Your Development Team
30mNavigating the hype-driven world of frontend development without going crazy - 'Kitze' Ristovski
22mHow to introduce new technology at work (and why you maybe shouldn't)
33mReact Advanced Patterns
26mCase Study - React Finland