Software Architecture for Humans!
Talkat JCON Europe 2023 · on Tuesday, 2023-06-20· at 13:00· Cinema 7, Im Mediapark 1, 50670 Köln, Germany·
summary
Argues that architecture succeeds only when it fits the people doing the work, offering a concrete model: compare system complexity to a team’s maximum capacity and either reduce dependencies or raise the team threshold by education. Demonstrates a real toolset: behavioral code analysis (Adam Tornhill) to find who changes what, debates static analysis vs autonomy, warns about gaming metrics with Gotthard's law, and proposes a requirements approach document listing trade-offs, experts, and concrete solutions instead of rigid micro-architecture rules.
AI-written summary · about
chapters (14)
- 0:00Welcome and introduction
- 1:18What is software architecture?
- 2:00Why humans need architecture
- 8:54Optimizing dependencies isn't enough
- 10:19Legacy systems and team knowledge
- 14:58Is legacy a social problem?
- 17:29Big ball of mud isn't always bad
- 22:27Who is a good developer?
- 26:41Complexity and developer praise
- 30:30Micro and macro architecture
- 37:42Requirements vs rules approach
- 42:59Inverse Conway maneuver limits
- 47:54Humans over org charts
- 49:19Conclusion and Q&A
related talks
45mSoftware Architecture for Humans!
46mTHE too MANY FACES OF ARCHITECTURE
48mArchitecture: The Stuff That's Hard to Change
49mWhy software architects fail: and what to do about it
45mFive things every developer should know about software architecture
45mFive things every developer should know about software architecture
37mArchitecting for Tomorrow: A Pragmatic Perspective
41mSoftware Architecture in a DevOps World