A Theory of Everything
summary
Argues that programming languages are not the unifier and that a practical unifying claim is values alignment: choose and operationalize values like debate decide and commit so front end (React Next.js Nuxt) and back end (Node.js, CloudFormation, AWS, containers) stop operating in silos. Lists concrete browser and infra tools (WebRTC WebGL WebSQL, Kinesis, Kafka) and reports that teams adopt values through a mini onboarding bootcamp and settle on about five-ish values, which proves effective.
AI-written summary · about
chapters (13)
- 0:00Start
- 8:04Benefits of Unification
- 8:41A Step Back
- 12:11What's Happening?
- 13:17The JavaScript Promise
- 13:59Is JavaScript Too Useful?
- 16:05#1 Question from Beginner Programmers
- 17:16Value: Declarative Over Imperative
- 17:55Value: Composition Over Inheritance
- 18:28Value: Convention Over Configuration
- 18:53Value: Users Over Everything
- 20:02What Are Your Values?
- 21:20Debate, Decide and Commit
related talks
21mEverything as Compiler
46mFunctional Frontend. Practical survival guide for backend engineers.
27mTheory to action: Architecting and implementing your team operating system
47mThe Meaning of LIVE
33mRethinking The Web Platform
01h 02mDDD Really Matters!
48mTechnical Modeling as a Practice
45mThe Silver Bullet Syndrome