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
What If Shakespeare Wrote Ruby 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/HTAZ/
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 the LA RubyConf 2015, the speaker explores the intersections between literature, specifically Shakespeare's work, and software development. Cuppy emphasizes the importance of language in both domains, explaining how Shakespeare crafted complex narratives with minimal directorial input. The session showcases how metaphor and abstraction, akin to the art of poetry, can enrich programming practices and enhance communication among developers. Key points discussed include: - **Engagement and Interactivity**: The speaker encourages audience participation, eliminating laptops to foster connection. - **Cuppy's Background**: He shares his journey from acting to software development, highlighting the value of creativity and interactivity in tech. - **Language and Poetry**: Cuppy likens software developers to poets, arguing that programming requires artistic expression to convey meaning through code. - **Shakespeare's Influence**: Cuppy details how Shakespeare, without explicit stage directions, created complex interactions in his plays, mirroring how software should express intent through its structure. - **Domain Specific Language (DSL)**: The concept of DSL is introduced as a method to unify communication among teams, emphasizing the importance of establishing clear conventions. - **Expressive Conventions**: Cuppy posits that Ruby's expressiveness allows for a more meaningful and creative coding experience, akin to a poet’s use of metaphor. - **Theater as a Model**: The discussion shifts to the theatrical performance, where actors deal with minimal scripts, paralleling the coding practices where engineers interpret and build upon precursors. - **Conventions in Code**: Finally, Cuppy explains how established coding conventions, such as relationships in Active Record, streamline collaboration and foster innovation while respecting written code. In conclusion, Cuppy invites developers to embrace their roles as 'software writers,' harnessing the power of language and metaphor to advance their field. By implementing expressive conventions in programming, much like Shakespeare’s poetic approach, developers can improve their communication, creativity, and ultimately, their productivity in software engineering.
Suggest modifications
Cancel
