Future Proofing your Ruby Stack
summary
Claims that security is the top priority backed by a concrete breach example: 10 million records leaked when a public DB was connectable to development. Upgrades are costly and slow — one migration took 26 weeks to upgrade. Infrastructure choices favor AWS/Heroku for uptime despite cost. AI use is pragmatic: an email‑parsing tool returns 98% accurate results and saves morning work. Staffing investments include one day a week for upskilling and phishing training that drops failures from ~50% to zero.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:49Not about technical details
- 3:14Ruby stacks: dev vs management
- 5:21Top 3 Ruby stack considerations
- 6:43Security risks and consequences
- 9:14AI’s impact on security
- 10:38Upgrading old Ruby versions
- 13:25Features vs upgrades balance
- 13:46Server costs and choices
- 15:11AWS and Heroku popularity
- 17:00Community contributions matter
- 17:43Upskilling developer time
- 19:09Documenting for future devs
- 20:13AI in Ruby apps
- 22:18Security and testing future-proofing
- 22:59Staff training and phishing
- 24:03Professional development time
- 25:07Ruby Silver certification
- 26:12Staff morale and productivity
- 28:19Summary
related talks
20mDefending Against Data Breaches, as a Practicing Ruby Developer
36mData Management with Ruby
57mBuilding a Modern Security Engineering Organization
40mRunning a Government Department on Ruby for over 13 Years
42mThe Future is Now: Leveraging the Cloud with Ruby
36mUsing Ruby In Security Critical Applications
43mIf security is hard, you are doing it wrong
42mThe world runs on bad software