Let the Junior Dev Upgrade Rails
summary
Tells how a junior dev runs multiple Rails upgrades from 3.x to 4.1, converts ~25 models/controllers to strong_parameters, writes tests to reproduce failures against a thousand‑line controller, and helps get Rails 3.3 deployed. Describes repeatedly rebased to master to reduce merge pain, contributing fixes and StackOverflow docs, spawning a utility now called strong_like_bull, and helping revive the project so the full test suite runs despite major layoffs.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 3:58First project as junior dev
- 7:09Types of junior developers
- 11:24Learning through Rails upgrades
- 14:31Tips for mentoring juniors
- 18:02Embrace mistakes and failures
- 21:12Strong parameters upgrade journey
- 23:18Career growth through Rails
- 25:03Key takeaways and conclusion
related talks
39mThe Long Ball - Upgrading long lived Rails apps from 1.x-4.0
35mChanging the wheels on the bus at 80 mph: Upgrading to Rails 3
28mUpgrading Rails: The Non-Technical Parts
29mUpgrading Rails at Scale
26mHow to be an Awesome Junior Developer
25mUpgrading Rails: Everyone can do it and here’s how
21mRails Upgrade Mastery: Best Practices for Large-Scale Enterprise Applications
38mOur Fight Against Super Bad Patterns in Legacy Rails Apps