Model Drift and Software Attractors
summary
Argues that architecture is emergent: business model drift forces software into a handful of software attractors, so up‑front optimization for cohesion or modularity often backfires. Uses a practical method—create a naive design, stress it via residuality, map real business information as simple left‑to‑right asynchronous flow‑based architecture call chains, then compress or share components consciously. Recommends tracing flows to code, using queues, FMEA and STRIDE to expose fragility.
AI-written summary · about
chapters (12)
- 0:00Introduction to architecture
- 1:55The myth of stillness
- 5:36Cause and effect confusion
- 10:15Architecture is emergent
- 12:44Historical context of control
- 16:14Conceptual clogging
- 20:00Model drift explained
- 21:46Software attractors
- 24:11Flow-based design
- 27:46Mapping information flows
- 33:04Emergent structures
- 34:19Conclusion and takeaways
related talks
59mDeliberate Architecture
51mSoftware Architecture for Humans!
45mSoftware Architecture for Humans!
49mWhy software architects fail: and what to do about it
33mSet Design: Putting the "Art" in "Architecture"
41mThe lost art of software design
57mSoftware Architecture: The Hard Parts
46mAchieving an evolutionary architecture through simplicity