Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
What if Shakespeare Wrote Ruby? by Adam Cuppy Did you know that Shakespeare wrote almost no direction into his plays? No fight direction. No staging. No notes to the songs. Of the 1700 words he created, there was no official dictionary. That’s right the author of some of the greatest literary works in history, which were filled with situational complexity, fight sequences and music, include NO documentation! How did he do it? In this talk, we’re going “thee and thou.” I’m going to give you a crash course in how: Shakespeare writes software. Help us caption & translate this video! http://amara.org/v/Lg6W/
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
In the talk titled "What if Shakespeare Wrote Ruby?" presented by Adam Cuppy at Rails Pacific 2016, the speaker explores the concept of creativity in software development through the lens of Shakespeare's writing style. With a professional background in acting and a strong appreciation for theater, Cuppy connects the expressive nature of Shakespeare's works to the principles of programming, particularly in the Ruby language. Key points discussed include: - **Shakespeare's Lack of Documentation:** Cuppy highlights that Shakespeare wrote extensively without detailed documentation or staging instructions, emphasizing the power of expressive language. - **Joy and Experience in Engineering:** The objective of Cuppy's talk is to bring joy to the audience, underscoring that everything done in software engineering is aimed at creating experiences for users. - **The Challenge of Documentation:** Cuppy argues that while documentation is necessary, it is often seen as tedious and unappealing, comparing it to a necessary evil within the programming community. - **Power of Language and Poetry:** Cuppy discusses the significance of language in both Shakespeare's works and programming, claiming that poetry serves as a form of documentation that expresses emotions and experiences clearly. - **Shakespeare as a Software Poet:** He posits that if Shakespeare were to write code, he would integrate meaning and expressiveness in a way that is both impactful and poetic. - **Learning from Shakespeare's Techniques:** The speaker investigates how Shakespeare's use of language conventions and metrical structures can inform how developers approach coding, highlighting the importance of metaphor and abstraction in programming, as well as maintaining simplicity in complex applications. Cuppy engages the audience through a live demonstration, asking participants to act out a scene from Romeo and Juliet, reinforcing the idea that understanding the interactions between individuals (or code elements) is crucial for successful communication in programming. In conclusion, Cuppy stresses that like the harmonious nature of Shakespeare's poetry, software development involves creating meaningful interactions that foster engagement and joy. The talk ultimately challenges developers to see themselves as poets in their craft, encouraging a mindset that prioritizes creativity and connection over rigid structure.
Suggest modifications
Cancel
