Give me that old-time pattern language
summary
Argues that pattern languages are literal three-part rules mapping context, recurring problem (an unbalanced system of forces) and solution, and reclaims Alexander’s original formulation for software architecture. Uses a physics vector analogy as the actual analytic tool, treating forces as directional magnitudes and aiming for the sum of the forces has to equal zero. Proposes designing patterns whose solutions explicitly restore balance; demonstrates how to model and verify that balance.
AI-written summary · about
related talks
43mPlain Pattern Language
52mMeta modern Software Architecture
47mExpressing Design in Code: Architecturally-Evident Coding Patterns
01h 00mPatterns for Software Architecture
50mMastering Visual Communication for Software Architecture
51mSoftware Architecture for Humans!
40mSystems Thinking for Developers
08mLightning talks – 101 Things Software Never Learnt