From Code to Complexity: Shifting to Systems Thinking in Software Development
summary
Argues modern software failures come from unchanged mental models, not just missing tech, and shows concrete moves: avoid distributed-monoliths (microservices can still couple), use cloud tools like autoscaling and caching as low-level leverages, redesign feedback loops to prevent unchecked growth, and change mindsets via cross-team experiments and collective modeling (event storming, whiteboards). Recommends five practices: Iceberg model, look for leverage points, systemic reasoning, metacognition, think well together, and treat tech skills (e.g., Flutter, Firebase) as necessary but not sufficient.
AI-written summary · about
chapters (4)
- 0:00Introduction
- 1:18Keynote "Don't hit the Iceberg" by Diana Montalion
- 42:43Diana answers questions from the audience
- 49:00Outro
related talks
36mFrom Software to Systems: Modern Agility
50mTactics and strategies on software development: how to reach ...
36mThe human factor you might be missing when designing your system
58mDon't Walk Away From Complexity, Run
56mKicking the Complexity Habit
49mSystems Thinking and the Art of Simplification -
40mSystems Thinking for Developers
52mMental Models, Complexity and Software