Ruby for Startups
summary
Starts from concrete rules: separate what changes, prefer composition over inheritance, and you ain't going to need it. Describes refactoring an app that handled thousands of email sends a day, moving work out of web requests into SQS/SQS2 queues, S3 for message content, Simple DB for logs, and EventMachine for async SMTP delivery. Recommends presenters, settings plugin, careful config strategies, avoiding premature scaling, and keeping business logic isolated so changes touch one module.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 6:19Design for Change
- 11:28Program to Interface
- 13:06Composition vs Inheritance
- 14:35Delegate
- 15:45Use the latest
- 16:22Fight all the time
- 17:22Focus on learning
- 18:20Move everything out of the web request
- 18:48Keep in the back of your mind
- 19:25Concurrency
- 19:48Event Machine
- 20:42Relational Database Relationship
- 21:19Alternate Database Systems
- 23:17Code Layout
- 23:49Configuration Variables
- 25:21boolean columns
- 25:43slates
- 26:04testing vs design
- 26:53other inbox
- 27:35designer
- 28:29presenter
- 30:53end
related talks
49mEnterprise Ruby - Let’s Talk Business!
32mruby best practice patterns
43mThe Clean Architecture: How to Grow From Startup to Enterprise
16mOne Ruby App to Rule Them All
01h 12mRuby Best Practice Patterns
33mStart writing Ruby (stop using classes)
46mClosing Keynote
17mDesigning software that maximizes developer productivity