The Art of Ruby
summary
Argues that beauty in Ruby comes from concrete constraints and refactors: uses a guessing‑game example to show extract method then extract class pattern, endorses rules like five-line methods and 100‑line classes, and measures improvement with Code Climate and Pull Review. Digs into a real bug in the Alchemist gem where Time.parse slows from ~3.7s to ~43s because method_missing builds a giant regex per call, removes method_missing, lazy‑loads modules, and restores performance to baseline.
AI-written summary · about
chapters (14)
- 0:00Introduction and speaker intro
- 1:01Defining art and programming
- 2:07Writing beautiful Ruby code
- 3:55Balancing complexity in methods
- 5:01Constraints and artistic freedom
- 6:29Breaking Ruby rules creatively
- 7:56Extracting classes for clarity
- 9:18Performance vs artistic code
- 13:47Refactoring for performance
- 15:50When Ruby isn't fast enough
- 16:11Building your coding toolbox
- 17:13Measuring and improving code
- 18:40Knowing when to break rules
- 19:43Summary and resources
