How to Protect Architectural Purity
summary
The talk explains how to protect a software system's clean architecture from entropy and new-developer mistakes by preventing incorrect dependencies between components and common class-design errors. It describes concrete preventive measures implemented early, using tests, IDE plugins and existing language features to automatically enforce architectural rules.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:12What is architecture
- 5:22System components
- 7:27Component interfaces
- 9:55Link control
- 14:44Architecture protection tools
- 23:34Architecture vs design
- 24:16Design protection
- 31:22Summary
- 34:41Resources
- 37:08Q&A
related talks
55mClean architecture that harms your code
52mEtiquette for Software Architects
56mClean Architecture: Deep Dive
51mClean Architecture: Why? How? For Whom?
49mWhy software architects fail: and what to do about it
49mAs Much Architecture Work as Necessary
51mClean Architecture: A Deep Dive
47mStep by Step Toward Clean Architecture