ruby best practice patterns
summary
Argues for concrete, small-scale refactorings: split big routines into composed method calls (example from Capistrano), use block-based execute-around patterns so IO.open always closes and will_paginate or Ruby 1.9’s tap make creation+lifecycle explicit, and convert repeated-argument code into a method-object (used to emit a DOT file) so shared state lives on the object. Recommends comprehensive tests before refactoring, cites Kent Beck/Smalltalk origins, and contrasts helpful patterns with a tongue-in-cheek “unfactor” anti-pattern.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:14Lone Star Ruby Conf 2008
- 0:44st Practice
- 14:00Capistrano
- 16:36Rubinius
- 18:31Will Paginate
- 20:00Ruby 1.9
- 21:45Method Trails
- 24:58Context
- 27:55Examples
- 28:34Try Them
