How to Make High-Quality Architectural Decisions
summary
Covers how to prevent and fix low-quality software architecture by introducing validation and iterative correction of architectural decisions. Describes problems caused by poor initial design, degradation during maintenance, and failure to accommodate new requirements, and presents practical ways to protect a project from these issues or recover a struggling codebase.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:25Why architecture matters
- 7:23Quality criteria
- 12:46Reusability in architecture
- 18:47Abstractions vs overengineering
- 21:34Developer experience
- 26:07Architectural oversight
- 32:13Legacy architecture
- 33:15Q&A
related talks
49mWhy software architects fail: and what to do about it
59mDeliberate Architecture
45mFive things every developer should know about software architecture
46mTHE too MANY FACES OF ARCHITECTURE
48mArchitecture: The Stuff That's Hard to Change
01h 10mDecisions We Make: A Personal View on Architecture
34mShortening the Architectural Feedback Loop
37mSoftware Architecture for Humans!