Software Architecture in a Scenario of Uncertainty
summary
Discussion of software architecture strategies for handling continuous change and uncertainty in digital initiatives. Covers planning techniques and architectural approaches that allow safe, evolvable systems despite unknown future requirements, aimed at practitioners responsible for applying technology effectively (mentions practical strategies to absorb ongoing changes).
AI-written summary · about
chapters (20)
- 0:00Introduction
- 3:23Defining software architecture
- 8:01Architect as tour guide
- 10:09Uncertainty and inevitable changes
- 11:58Evolutionary architecture
- 15:13Breaking organizational silos
- 18:27Projects vs products
- 19:52KISS principle
- 21:18Essential vs accidental complexity
- 24:58Technical debt and maintenance
- 27:07Testing culture
- 27:52Reversibility principle
- 29:22Delaying decisions
- 31:31Big Four Design vs Pig Renan
- 34:21Avoid unnecessary complexity
- 36:30Pareto 80/20 rule
- 37:37Architect not dictator
- 38:41Architecture as evolution
- 39:45Real migration case
- 43:41Gradual constant evolution
related talks
38mPractices for Effective Continuous Software Architecture
45mFive things every developer should know about software architecture
02mThe architecture of uncertainty
45mDemocratising Software Architecture
57mSoftware Architecture: The Hard Parts
58mThe past, present and future of Architecture
14mThe Evolution of Evolutionary Architecture
43mSoftware Architecture, Design Thinking & Knowledge Flow