Firefighting on Rails

on YouTube ↗27m

" summary

Rails parses a web status board every 30 seconds with Mechanize, stores incidents in MongoDB, and pushes SMS and email via Twilio and SendGrid on Heroku; claim: a weekend prototype replaces loud pagers with quiet, personal notifications and clickable maps. About 250 volunteers across 14 stations adopt it, cutting lookup time and shifting behavior until map skills atrophy. Code is ugly but effective: addresses, cross streets, and notes arrive as concise messages and crews get to scenes faster.

AI-written summary · about

" chapters (7)

1. 0:00Firefighting and Rails intro
2. 3:22Volunteer fire service challenge
3. 8:23How pagers work
4. 12:54One-weekend solution
5. 18:47Worst code biggest impact
6. 22:36Solving over perfect code
7. 25:51Give back to community

" related talks

• 29mRealtime web applications with streaming RESTBrad Gessler · RailsConf 2012
• 41mOff the Tracks - Challenging the Rails MindsetNick Sutterer · RubyConf AU 2013
• 34mIndustrial RailsChristian Weyer · RubyConf Portugal 2015
• 28mBuilding in Rails, Backbone, and CoffeeScriptDerrick Ko · Rocky Mountain Ruby 2012
• 28mRESCUE SQUAD: Rails Edition!Ben Lovell · Ancient City Ruby 2015
• 30mSelf-Care on RailsBen Greenberg · RailsConf 2021
• 17mActiveSupport::Notifications and Live Status PagesMatthew Delves · Red Dot Ruby Conference 2014
• 25mCivic Hacking on RailsWilliam Jeffries · RailsConf 2015