From massive pull requests to trunk-based development with Ruby
summary
Explains how a small Ruby team moves from long-lived PRs to trunk-based development by using flipper feature flags to ship incomplete work to 2% of users, relying on a continuous integration server to block bad commits, and sending runtime events via ActiveSupport notifications into CloudWatch dashboards. Describes concrete code snippets, handling Rails/Ruby upgrades by running two boots in parallel, and reports that shorter branches plus monitoring noticeably reduce merge pain and production surprises.
AI-written summary · about
chapters (10)
- 0:00Introduction to massive pull requests and trunk-based development
- 4:27What is trunk-based dev
- 8:07Overcoming fears about trunk-based dev
- 12:05Why CI is essential
- 14:14Monitoring prod with feature flags
- 17:26Trunk-based dev for any team
- 20:15Optimizing dev pipelines
- 22:24Understanding Dora metrics
- 27:50Experimenting with trunk-based dev
- 29:39Q&A
related talks
49mRuby Software Continuously Delivered and Exhaustively Explained
34mShitlist-driven development and other tricks for working on large codebases
51mFrom the Trenches - Remote Scaled Trunk-Based Development
32mPragmatic Community Driven Development in Ruby
01h 22mBreaking Down the Barrier: Demystifying Contributing to Rails- 34mShitlist-driven development and other tricks for working on large codebases
35mA Tale of Two Codebases
46mLightning Talks