Reinvesting in Ruby
summary
Shows that Ruby can evolve by actually wiring together dry-rb gems to build a blog in 15 minutes, using dry-system, dry-web-router, dry-view, dry-types/struct, dry-validation, dry-monads and dry-transaction for validation, result handling and composed business steps. Code is small, functional objects with constructor injection, repositories and explicit boundaries so tests run fast and isolated. Teams at IceLab adopt it in production, ROM and Hanami interop exists, yielding a change-positive architecture that proves maintainability at scale.
AI-written summary · about
chapters (33)
- 0:00Start
- 0:23Present Ruby Different Ruby Future Ruby
- 0:41We've come a long way
- 2:42Challenges
- 4:45Transition
- 5:08Complacency
- 5:34Tools
- 5:54Culture
- 6:55Open source communities are non-exclusive
- 7:14Reconsider Ruby
- 7:31Ruby moves slowly
- 8:26Ruby is ours
- 8:57Ruby evolves
- 10:40Code time!
- 10:54Functional Ruby
- 11:35Functional objects
- 11:55Separate data from behaviour
- 13:252 Object dependency management 3 Views
- 23:42Change
- 25:42Isolated testing
- 26:07Simplicity
- 26:24Clear separation of concerns
- 26:34Design around boundaries
- 27:27Design for the domain
- 27:53Ruby, melting pot
- 29:43Levelling up
- 30:39Better developers, better executing team
- 30:51Ship without guilt
- 33:07Deliver faster
- 34:29Hanami dry-validation & rom-rb
- 36:31Criticism
- 36:57Cooperation
- 37:43Celebration
related talks
27mA New Ruby Toolbox
35mReal-world Functional Ruby
01h 01mCan We Still Innovate?
44mReal-World Functional Ruby
39mFunctional Architecture for the Practical Rubyist
42mTaking inspiration from the functional world
50mWhat I Talk About When I Talk About Ruby- 39mFunctional Architecture for the Practical Rubyist