Listening to the design pressures
summary
The label non-functional requirements is misleading because these concerns actually program behavior and determine architecture; think of them instead as quality attributes like high performance, resilience, security and usability. The talk shows architectures that emerge when those attributes are binding: applied design patterns for low latency and redundancy, threat modeling and usability validation, and working practices that cull that which does not deliver. Concrete claim: strong nonnegotiable qualities produce repeatable, surviving designs.
AI-written summary · about
chapters (4)
related talks
01mListening to the design pressures
44mDeliberate Architecture
59mArchitectural Principles: Building the Foundations of Design Excellence
46mPractical (a.k.a. Actually Useful) Architecture
08mLightning talks – 101 Things Software Never Learnt
37mArchitecting for Tomorrow: A Pragmatic Perspective
41mThe lost art of software design
04mLen Bass Interview