David and Goliath, Ruby and the Enterprise
summary
Describes concrete wins and traps: a Java system on ~120 machines is refactored to ~40 app processes cutting server cost from about $30k/month to $5k/month and maintenance to one developer, while another project leaves 50 people idle for two days because one remote key holder goes on leave. Recommends two‑pizza teams, real‑time chat (Campfire/Skype) instead of email, and notes JRuby IronRuby Rubinius plus AWS SDK as practical integration paths.
AI-written summary · about
chapters (34)
- 0:00Introduction
- 0:53Big Round
- 1:59Guilty Technologies
- 2:56Enterprise
- 3:24Ruby
- 4:16The Enterprise
- 5:05Python vs Ruby
- 5:34Ruby and Rails
- 7:31Ruby as a language
- 8:29Metrics
- 8:59Rails
- 10:42JRuby
- 11:14Perception of Ruby
- 11:28Large companies
- 12:27Language
- 13:23Process
- 13:37Communication
- 13:54Hierarchical Structures
- 14:53Formal Parties
- 15:12Pizza Teams
- 15:43Keeping Teams Phone
- 16:07Accountability
- 17:22Keeping communication going
- 18:20Respect
- 19:05Confidence
- 19:52Adaptability
- 21:13Status
- 21:29Political Structure
- 21:56Failures
- 24:00Internal Influence
- 24:34Success Stories
- 25:38Application Processes
- 27:56Documentation of Success
- 28:35Education
related talks
01h 03mRuby at Scale
26mMonolith-ifying perfectly good microservices
46mRuby in the Cloud
21mTaming Monoliths Without Microservices
17mDesigning software that maximizes developer productivity
27mScaling Ruby Applications: Challenges, Solutions and Best Practices
30mMonolith-ifying perfectly good microservices
29mTime to Move Away from Ruby