Crafting Rails Culture
summary
Migrates legacy apps from Ruby 1.8/Rails 2.0 to current versions over two years and measures the gains, fixes breakages between Ruby trunk and Rails, builds and open sources me_test gem for faster in-test inspection, uses Capybara and power_assert for richer failures, replaced memcached client to resolve session and performance issues, documents three concrete admin-integration strategies (namespace, engine, separate app) and reports working production results across a 300-person company.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:23Ruby community contributions
- 6:02Company organization challenges
- 7:32Ruby chosen for development
- 11:57Rails development setup
- 12:39Rails benefits for architecture
- 15:54Open source Rails culture
- 17:45Admin integration solutions
- 20:59Sustainable Rails growth
- 22:03Team collaboration practices
related talks
38mOur Fight Against Super Bad Patterns in Legacy Rails Apps
22mRiding Rails for decades
35mChanging the wheels on the bus at 80 mph: Upgrading to Rails 3
29mUpgrading Rails at Scale
21mRails Upgrade Mastery: Best Practices for Large-Scale Enterprise Applications
26mKeeping the Rails Magic Alive After 18 Years
36mWorking Compassionately with Legacy Code
24mThe Rails Features we Loved, Lost, and Laughed at