The Timeless Way of Building
summary
Argues that software design patterns descend from Christopher Alexander’s architectural pattern languages and that fluency matters: misapplied patterns create antipatterns. Shows Rails/Ruby specifics—ActiveRecord brittleness, fat models, big ball of mud, brittle tree-walking vs extracted collaborators, awkward generators and untested migrations—and cites built examples (the Orgon campus experiment, Jalina Nuovo) where pattern-heavy designs fail to produce the intended quality without a name. Recommends reading Alexander to learn the why not just the how.
AI-written summary · about
chapters (21)
- 0:00Intro
- 1:05CARGOSENSE
- 2:23PATTERN NAME
- 3:34PATTERNS?
- 4:22ALEXANDER'S QUEST How can you distribute responsibility for design through all levels of a large hierarchy. while still maintaining consistency and harmony of overall design
- 7:03PRINCIPLES ARE PATTERNS
- 7:21SRP SINGLE RESPONSIBILITY PRINCIPLE
- 7:52DIP DEPENDENCY INVERSION PRINCIPLE
- 10:23WORKING WITHIN THE LANGUAGE OF CLASSICAL ARCHITECTURE
- 12:08CRAFSTMEN
- 12:45PROBLEM: TOO MANY PEOPLE THINK THAT DESIGN PATTERNS IN SOFTWARE MEANS A UBRARY OF CODE TEMPLATES
- 13:28WHAT ARE WE STRIVING TOWARDS?
- 16:45Walking the Tree
- 17:23COMPOSITION
- 17:39FAT Models
- 18:38PLUGINS* GEMS
- 19:10RAILS IS A SERIES OF VERY LARGE TUBES LIBRARIES
- 20:34TYPOGRAPHIC REFACTORING
- 20:51MVC
- 21:10UNTESTED CODE
- 22:56IT'S ABOUT SPEAKING A LANGUAGE
