Progress
summary
Progress comes with concrete tradeoffs: REST, Bundler and the asset pipeline change APIs and deploys, Ruby 1.9 adoption still leaves about one third of rooms on older interpreters, and many teams resist Rails 3 and CoffeeScript because upgrades break production workflows. Bundler and the pipeline reduce dependency and asset pain for teams that adopt them, while behavioral experiments show reframing reduces loss aversion, shifting reactions from fear to curiosity and making disruptive upgrades more likely to succeed.
AI-written summary · about
chapters (28)
- 0:00Progress and cooking inspiration
- 1:12Progress keeps Rails alive
- 2:18Abstract vs concrete discomfort
- 4:26Progress that makes people uneasy
- 5:52Ruby 1.9 upgrade skepticism
- 6:36Bundler’s controversial intro
- 7:19Rails 3 upgrade challenges
- 8:00Asset pipeline struggles
- 9:05CoffeeScript objections
- 10:32Measuring progress objectively
- 12:50Rails improved code clarity
- 13:35From curiosity to suspicion
- 15:02Traumatic events vs progress
- 20:00Aging and fear of change
- 21:47From hippie to Mr. Mature
- 24:17Tech knowledge aging fast
- 26:28Loss aversion roots conservatism
- 28:59Protect newbies vs stunt growth
- 31:30Easy Bake Oven analogy
- 33:41Real skills need real challenges
- 35:30Mr. Mature and Mr. Dummy alliance
- 36:55No speed limit to learning
- 38:20Hack brain against loss aversion
- 41:57Reframe mindset stay curious
- 42:38Build tools you care about
- 44:27Pain as part of progress
- 45:49Mantra against fearing change
- 46:09Summary stay young stay curious
related talks
35mChanging the wheels on the bus at 80 mph: Upgrading to Rails 3
29mLessons From A Rails Infrastructure Team
23mRails Frontend Evolution: It Was a Setup All Along
01h 09mRails 3 ...and the real secret to high productivity
29mUpgrading Rails at Scale
59mRailsConf 2011, David Heinemeier Hansson
39mThe Long Ball - Upgrading long lived Rails apps from 1.x-4.0
28mUpgrading Rails: The Non-Technical Parts