Engineering excellence starts on edge
TLDR
- Elite teams run production code on unreleased framework versions (edge) to co-create tools, not just consume them.
Key Takeaways
- Shopify, GitHub, and 37signals ran Rails 8.1 edge code in production for nearly a year before the first beta released at Rails World.
- Running on edge forces teams to find and fix bugs in real workloads; automated testing plus diligent programmers caught virtually all issues before they hit production.
- The practice shifts a team’s identity from open-source consumer to real-time co-creator, which DHH calls a “step function in competence and prowess.”
- Engineers who can immediately ship improvements they helped write stay more engaged, go deeper, and build direct connections to framework experts.
- The argument applies beyond Rails: any team using Ruby, Rails, or other open-source stacks can adopt this posture.
Why It Matters
- Two of the highest-scale web apps in the world (Shopify and GitHub) validate that edge production use is tractable, not just a hobbyist experiment.
- Waiting for stable releases creates a lag loop: teams can’t use fixes they helped write until the next version ships, breaking the motivation cycle.
- For founders and engineering leads, this reframes framework participation as a talent and culture lever, not just an open-source obligation.
DHH · 2025-09-06 · Read the original
