Don't Settle for Poor Names (or for Poor Design)
summary
Claims that naming drives design and shows it on a real Rails app (QCloud) with a 500,000‑line codebase and ~300 models, using Ruby on Rails and Postgres. Replaces four repeated DB columns with a value object named attribution event, implemented with Rails’ composed_of and a custom Concern, adds a factory-style build and a capture method, prevents subtle bugs, makes adding a new discarded event trivial, and demonstrates the small refactor steps that actually work.
AI-written summary · about
chapters (7)
- 0:00Start
- 4:43Designing
- 11:45An attribution event identifies a user anda has a timestamp
- 19:13How do we {log, capture, assign, save, or record} an attribution event?
- 21:37Example from QCloud
- 25:21Simple a Design
- 30:02Don't Settle for Poor Names
related talks
39mExploring Rails anti-patterns
41mOff the Tracks - Challenging the Rails Mindset
37mBuilt to last: A domain-driven approach to beautiful systems
36mRiffing on Rails: sketch your way to better designed code
31mIf it bleeds, it leads
36mRiffing on Rails: sketch your way to better designed code
01h 47mWorkshop - Applications First, Frameworks Second: Better Systems through Design
32mRails Sustainable Productivity