Set Design: Putting the "Art" in "Architecture"
summary
Argues that treating software like a building leads to waterfall, classist architects and instead models architecture on set design as agile architecture: concrete anecdotes (a last-minute harness fix, a minimalist play that still finds three staging positions, a muddled Stuart Little redesign) show choices about where code lives (MVC boxes, presenters, service objects), how teams iterate (rehearsal reports, tech rehearsals), and why Ruby’s monkey patching as empowerment lets teams own and evolve macro structure.
AI-written summary · about
chapters (42)
- 0:00Introduction
- 2:26Costume Design
- 3:10Theater Skills
- 3:26Telling the Story
- 5:40What Matters
- 6:00Business Value
- 6:30Software Architecture
- 7:12The 10X Developer
- 10:10Software Architectural
- 10:40Building Metaphor
- 11:01The Merry Widow
- 12:23ModelViewController
- 15:22Making my code more useful
- 15:47Liveable code
- 16:07Scary errors
- 16:57Minimalism
- 17:15Box Architectures
- 17:38Stuart Littles of Kids Play
- 18:35Making Changes
- 18:53Michaels Advice
- 19:34Building the Set
- 20:08Dont try to do everything
- 20:23I dont trust them
- 21:16My favorite show
- 21:50Where the actors went
- 22:07Back wall
- 22:28Macro structure
- 23:14Maintaining the architecture
- 23:53Too much architecture is stifling
- 24:14The wrong way
- 24:30Process rather than product
- 24:48Waterfall
- 25:08Rehearsal Reports
- 25:35Technical Rehearsal
- 26:27Traditional Building Metaphor
- 27:10Future of Ruby
- 27:47Monkeypatching
- 28:46Humility
- 28:58Making mistakes
- 29:38Meaningful architecture choices
- 30:05Betsy Haibel
- 30:55Fun Fact
related talks
24mThe too many faces of Architecture
01h 01mArchitecture: The Stuff That's Hard to Change
01h 09mAgile Software Architecture
01h 02mThinking Like an Architect
40mThe (too) many faces of architecture
41mArchitecture and Agility: A Shared Skillset!
45mArchitecture: The Stuff That's Hard to Change
59mDeliberate Architecture