Every Software Org is Dysfunctional
summary
Claim: every organization that builds software is inherently dysfunctional and architecture must be designed to live with that mess, not eliminate it. Examples: move to cloud after replacing expensive boxes with 7,000 cheap servers; microservices and continuous deployment enabling 50 deploys a day; LLMs and GenAI act as external stressors requiring guardrails; a successful intervention is taking a team offsite to build a contrived project and reintroduce new practices as proof — shows work where templates fail. Show don’t tell and design for feedback are decisive.
AI-written summary · about
chapters (9)
- 0:00Intro
- 4:57Dysfunction is human — It's the feature, not a bug
- 10:11The decision trap: Why how you decide matters more than what you decide
- 17:15Quantum mechanics turns 100 — What does it mean for SW architecture?
- 22:23From Sun Microsystems to the cloud: How hardware shapes SW architecture
- 27:03Architect as diplomat: Navigating legacy, teams & org boundaries
- 36:00Will AI replace the architect — or just amplify their blind spots?
- 41:03Gen AI as a stressor: Protecting your SW architecture from the outside in
- 44:30Outro
related talks
52mUnderstanding UnHealthy Syndromes of Software Delivery
18mBuilding Platforms, Breaking Code How Your Org Chart Can Support or Wreck Progress
43mSoftware Architecture, Design Thinking & Knowledge Flow
43mSoftware Eats Culture For Breakfast
01h 01mFrom 'Agile Hangover' to 'Antifragile Organisations'
30mThree value inhibiting dysfunctions of enterprise software development
35mOrganization: A Tool for Software Architects
41mYour Systems Aren't Stuck - Your Teams Are