Talks
Speakers
Events
Topics
Search
Sign in
Search
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
search talks for
⏎
Suggest modification to this talk
Title
Description
Set Design: Putting the "Art" in "Architecture" by Betsy Haibel I thought of software architects as petty waterfall dictators. Then I became one. My theater background saved me. In this talk, we’ll look at set design — an ongoing, collaborative process — as a model for a more agile kind of “architecture” than building metaphors allow us. You’ll learn about the most important part of any architecture (hint: people), about using architecture to foster team creativity, and about the agile-architecture superpowers that Ruby gives us. No matter your title, you too can architect!
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
The video titled 'Set Design: Putting the "Art" in "Architecture"' presented by Betsy Haibel at RubyConf 2017 explores the relationship between theater set design and software architecture. Haibel contrasts traditional hierarchical approaches to software design with more agile and collaborative methodologies akin to those used in theater. Key points discussed in the video include: - **Flawed Metaphors**: Haibel argues that many common metaphors for software architecture, particularly the building metaphor, are inadequate as they promote a rigid hierarchy. - **Theater Experience**: Drawing from her background in theater, she discusses how collaborative problem-solving is essential in set design, which parallels effective software architecture. - **Value of Collaboration**: She emphasizes that the design and implementation process in both fields should involve all stakeholders to meet creative and functional needs. - **Storytelling in Code**: Haibel likens the importance of 'telling the story' in theater to focusing on business value in software development, advocating for code that prioritizes usefulness over perfection. - **Impact of Architecture on Choices**: She illustrates how architecture influences engineers' decisions and emphasizes the need for flexibility and meaningful choice within architectural frameworks. - **Learning from Mistakes**: Personal anecdotes highlight the value of iterative learning processes in both theater and software development, with an emphasis on trusting team members' creativity and expertise. - **Agility Over Rigidity**: The talk concludes with a call for embracing agile methodologies that foster communication and adaptability, contrasting this with the limitations of the waterfall approach. Haibel encourages developers to see themselves as architects regardless of their titles, emphasizing the collective responsibility for architecture and the significance of empowering each team member to contribute creatively. She advocates for a shift from strict architectural control towards a more collaborative and flexible development environment.
Suggest modifications
Cancel
