The architecture of uncertainty
summary
Argues that the common response to uncertainty — piling on abstractions and flexibility — usually makes systems worse and more complex rather than future‑proofing them. Claims designers should treat code as executable fiction, make explicit paradigm choices (C and Java are both high level), and use uncertainty and lack of knowledge to drive the schedule by deferring decisions and preserving real options rather than premature generality. Practical takeaway: avoid complexity.
AI-written summary · about
related talks
44mSoftware Architecture in a Scenario of Uncertainty
58mDon't Walk Away From Complexity, Run
49mGetting a handle on software architecture
47mThe Philosophy of Architecture
56mKicking the Complexity Habit
49mWhy software architects fail: and what to do about it
41mBeyond "it depends" - How much architectural work do we need?
45mFive things every developer should know about software architecture