Design Patterns And The Proper Cultivation Thereof
summary
Argues that design patterns are useful as directional targets while practicing evolutionary design: uses TDD, stepwise refactorings (not wholesale pattern implants), and the four rules of simple design (tests pass, reveal intent, DRY, small). Describes building a sticky‑papers app that ends up visitor-ish by extracting methods then classes, shows concrete refactorings like extract method and class extraction, recommends refactoring to patterns as a how‑to, and warns to avoid Singleton and not to name classes after pattern names.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:14Cory Hanes
- 5:51Design Patterns
- 13:00Kent Beck
- 13:21The Four Rules of Simple Design
- 15:07No Duplication
- 20:02Refactoring to Patterns
- 26:53Factory Methods
- 36:41Suggestions for Avoiding Newbie Pattern Madness
- 47:12Chain of Responsibility
related talks
26mPatterns, patterns everywhere
30mDesign Thinking for Rubyists
32mruby best practice patterns
39mFunctional Architecture for the Practical Rubyist
32mUndervalued: The Most Useful Design Pattern
32mN design patterns you might actually use
38mRefactoring Fat Models with Patterns- 39mFunctional Architecture for the Practical Rubyist