The Ten Commandments of the Ruby Programmer
summary
Practical Ruby development rules focused on concrete techniques: keep domain objects free of framework coupling (avoid leaking ActiveRecord or mailers into core logic); remove duplication by extracting gems or higher‑level abstractions; avoid nil via constructor validation, Null Object, or optional patterns; replace long if/else chains with polymorphic transaction objects that share an interface; minimize mocks; and enforce quality with tests, daily refactoring, code reviews and pair programming.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:40About commandments and best practices
- 8:15Avoid object promiscuity
- 11:08Control nil usage
- 14:24Reject unnecessary ifs
- 17:38Mocks as design signal
- 20:10Build quality from start
- 22:54Refactor daily
- 25:20Team programming
- 27:07Challenge references
- 28:59Unlearn to learn
related talks
36m"Business Logic in Ruby"
49mMy Dog Taught Me to Code
39mTalmudic Gems For Rails Developers
41m"Tackling complex architecture in Ruby"
32mRails Sustainable Productivity
40mWorkshop - Simplifying Code: Monster to Elegant in Less Than 5 steps
44mRuby Libraries Important for Rails
33mDo the Right Thing: Practical lessons for your..