Riffing on Rails: sketch your way to better designed code
summary
Claim: sketching design directly in a single Ruby scratch file yields rapid, low‑cost iterations that expose names responsibilities and relationships and surfaces unknowns. The method prototypes controllers and models (examples: favorites controller, team buckets and credit records), leans on Rails conventions and APIs including signed GlobalID, and deliberately skips migrations/tests/files so ideas change cheaply. Sessions run about 40–60 minutes with ~5–10 minutes to reach flow, and pairing produces sharable, near‑runnable artifacts and clearer decisions.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:05Code design importance
- 3:33What riffing is
- 8:30Riffing benefits
- 14:11Riffing obstacles
- 17:25Live demo: credit system
- 28:29Collaborative riffing
- 33:12Tips for riffing
- 35:44Closing
related talks
41mOff the Tracks - Challenging the Rails Mindset
01h 47mWorkshop - Applications First, Frameworks Second: Better Systems through Design
40mMaking a Rails App with 140 Characters (or less)
32mRails Sustainable Productivity
39mExploring Rails anti-patterns
34mSimple and Elegant Rails Code with Functional Style
31mIf it bleeds, it leads
34mCode Spelunking: teach yourself how Rails works