Paradigm Lost
summary
Argument: the old front/back CRUD model is breaking and four concrete shifts matter: local‑first (edge functions plus embedded DBs like SQLite or DuctDB to eliminate spinners and work offline), async orchestration (use Temporal instead of brittle GitHub Actions to implement one‑click buy and recover from failures), data engineering (data volume grows ~5x in three years so data engineers outpace JS jobs), and AI/software‑2.0 (prompt engineering moves accuracy from ~17.7% to ~78.7%; tools like Copilot/AlphaCode already produce competitive code).
AI-written summary · about
chapters (10)
- 0:00Introduction and motivation
- 1:07State of JavaScript vs salaries
- 2:28Talk structure and full stack definition
- 5:14Theory versus practice in full stack
- 6:16Real-world app expectations
- 9:42First paradigm: Local-first
- 13:15Second paradigm: Async programming
- 18:06Third paradigm: Data engineering
- 22:22Fourth paradigm: AI and software 2.0
- 26:51Conclusion and summary
related talks
01h 10mThe Future of Frontend Panel
29mApps, Stacks, and Frameworks: Avoiding “Shiny Object” Syndrome
30mEngineering in Overdrive: How to Thrive When Tech Evolution Goes Full Gas
40mFront end development in 2040
38mThe Front End Architecture Revolution
36mWe're gunna program like it's 1999
29mThe Front-end Takeover
45mJump to Hyperspace: Light Speed, User Agency & Moving Past the Cloud