Lightning Talks - Part II
summary
Lightning round of concrete takeaways: draw your engine routes on the engine itself and use isolate_namespace so engine and app routes coexist; aim for precompiled Ruby binaries (Tokaido / Railcar) to avoid local compile failures — five install steps at 95% each yields only ~77% success; provide URL helper prefixes for engine tests. Use symmetric_encryption with AES‑256 unlocked by an RSA key to keep prod keys out of source. Monitor with Graphite dashboards (2,000 workers, peaks ~10,000) and parallelize tests for fast feedback.
AI-written summary · about
chapters (18)
- 0:00Start
- 0:25Greg Belt - Seven Tips for running an Open Source Project.
- 1:27Ryan Biggs - Integration testing engines
- 4:55Yehuda Katz - Tokaido
- 9:25Ryan Brunner - Seven reasons why you should help organizer your local user group.
- 14:20Mike Scalnik - Railcar
- 16:27Felix Dominguez - Why you don't get hired
- 20:53Reid Morrison - Rails Encryption
- 26:11Evan Dorn - Ninjascript
- 27:00Jay Moorthi - tddium
- 31:44Rod Paddock - How I saved the World with Ruby and Nokogiri
- 34:15Richard Schneeman - Wizards from WTF to Wicked
- 36:42Sam Woodard - flash_s3_rails
- 40:36Charles Lowell - One Man in the name of Embedding Javascript into Ruby
- 44:37Matt Rogish - Hacking the Airlines
- 49:08Brad Wilkening - Top 10 Reasons you should probably quite your job
- 54:08Matt Conway - Monitoring with Graphite
- 58:51Dr. Nic Williams, Evan Phoenix - It's a Wrap!
