Software Design as Story Telling: Reflecting on the Work of Italo Calvino
summary
Maps Calvino’s five memos onto concrete software practices and claims: treat complexity by intentionally killing Medusa by reflection to keep designs light but not superficial; accept controlled uncertainty and underspecification instead of overengineering; favor deliberate waiting and competence for true rapidity; use diagrams and reverse/roundtrip engineering to improve visibility and shared models; and manage variant architectures as multiplicity with four practical patterns (single-inspiration, intersecting narratives, unifying visions, aphoristic collections). The paper proposes these mappings and suggests specific agile refinements.
AI-written summary · about
chapters (9)
- 0:00Storytelling in software design
- 1:14Calvino’s Six Memos for software
- 3:03Inspiration and style in storytelling
- 5:03Lightness handling complexity
- 8:19Rapidity in development
- 10:35Precision versus vagueness
- 12:32Visibility in software
- 14:55Multiplicity in code
- 17:14Key takeaways
related talks
02mDesign after Agile: How to Succeed by Trying Less
53mSoftware Design: Beyond Boxes & Lines
41mThe lost art of software design
41mHow We Tell Stories In Code
01mSoftware doesn't tolerate ambiguity
52mFrom Code to Complexity: Shifting to Systems Thinking in Software Development
01h 27mPlato, Magritte, Sartre & Carroll - Learning Software Design from the Masters
59mModelling Stories of the Beautiful Mess