Ruby on Rails - The Single Engineer Framework
summary
Claims that a product can be built and run by one engineer using Ruby on Rails for the backend and React Native mobile client for iOS and Android, with Rails engines and gems (ActiveRecord, ActiveStorage, Sidekiq, Flipper, ViewComponent, Blazer) providing batteries‑included features. Describes the startup Angry Building renamed Leo, where a single developer produces 400 web screens and ~10 mobile screens, favors reuse and i18n, explains invent vs buy decisions and shows the architecture actually shipping and operating in production.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:07Why Rails still matters
- 6:26Rails as single-engine framework
- 13:51Real-world Rails success
- 15:40Battery-included & convention over config
- 20:55Extensible platform & Rails engines
- 25:08Ruby quirks & readability
- 36:30Rails overview & learning resources
- 37:34Closing & Q&A
related talks
32mHow I architected my big Rails app for success!
18mReact-ing to Rails: Why Ruby on Rails is the best Stop for Web Developer
42mHow Rails fosters a diverse and competitive tech ecosystem in the era of big tech
46m365 Days Later: Moving from Java to RoR and how it changed everything
35mReact Native & Rails, A Single Codebase for Web & Mobile
34mIndustrial Rails
14mWhat About Ruby On Rails? ... From A PHP Guy
40mOptimize for developer speed