Lightning talks – 101 Things Software Never Learnt
summary
Argues that applying building-architecture myths to code causes brittle designs and bloated constructors with dozens of dependencies; claims real architecture emerges early and iterates rather than being finished up front and insists on measuring composition by relationships not isolated parts. Recommends process-oriented not product-driven design: discover constraints, favor simplicity through interaction of small components, let the system grow from its environment, and tolerate the anxiety of not knowing rather than locking decisions too soon.
AI-written summary · about
chapters (4)
related talks
08mLightning Talk: Breaking the Mold: Unveiling Anti-Architectural Patterns in...
49mWhy software architects fail: and what to do about it
37mSoftware Architecture for Humans!
45mFive things every developer should know about software architecture
25mBuilding Castles, Not Sandcastles: Strategies for Software Architecture Success
33mClosing Keynote
51mA Contrarian View of Software Architecture
37mArchitecting for Tomorrow: A Pragmatic Perspective
