What's Next? The past, present, and future (All Dev, No Ops)
summary
Founder of Sentry traces web tooling from PHP to Django/Rails to React and Next and makes concrete points: Next gives instant deploy URL per branch and enables easy canaries but real traffic shadowing fails because stateful databases and connections remain bottlenecks; Sentry is built to capture JavaScript errors and production telemetry when logs are absent; modern builds push bundle size a few MB to clients; industry solves shipping speed but still lacks reliable monitoring for JS in prod and database-locality solutions.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:48Early 2000s PHP and FTP
- 2:54Scaling PHP and frameworks
- 4:43Rails and Django era
- 6:50Century in Heroku era
- 8:11Mobile apps and interactive web
- 9:59React and Next.js
- 11:46Dev vs user experience
- 13:56From Subversion to Git
- 16:02Need for monitoring
- 17:50Century’s monitoring
- 19:56Future dev bottlenecks
- 21:39Database and state issues
- 23:23Reinventing tooling
- 24:45Next.js lifecycle
- 25:28Closing thoughts
related talks
38mSentry as a way not to be afraid
21mProduct Decisions for Building a PLG SaaS Company
44mThe Next Generation of Developer-First Products
27mFundamentals of Front End Ops
33mFrom “its broken” to “fix is out”
58mDevOps for Frontend Engineers
38mSolutions at Scale
23mObserving your applications with Sentry and Prometheus