Ruby Best Practice Patterns
summary
Argues that applying concrete Ruby patterns like compose method and around filter makes code easier to read, faster to change and lowers risk, while demonstrating the opposite—unfactoring—by inlining Capistrano deploy steps, inlining scm run, and renaming identifiers (even pig latin) so code still passes tests but becomes maintainable only by its author; shows tools and examples from Rails, Capistrano, Rubinius, will_paginate and Graphviz, mentions roughly 30 or 40 pattern variants and that unfactoring sometimes takes three or four nights to achieve.
AI-written summary · about
chapters (10)
- 0:00Ruby best practices intro
- 5:49Unfactoring patterns
- 19:54Why patterns matter
- 25:13Compose method pattern
- 30:51Execute around pattern
- 33:21Yield and return pattern
- 37:57Command object pattern
- 41:08Creating Ruby patterns
- 57:07Best practices & team rules
- 1:04:25Q&A
