Shall I Compare Thee to a Line of Code
summary
Compares poetry forms to programming practices and argues that constraints help structure thinking: sonnets require 14 lines, three quatrains, volta and couplet and iambic pentameter, which forces a logical turn; free verse maps to flexible frameworks. Uses Ezra Pound’s two-line poem and Shakespeare’s sonnet as concrete examples, shows Rails source code visually mirroring stanzas, and recommends workshop-style silent feedback plus ruthless revision. Advocates balancing functionality and readability — say a lot with a little — and cites the 2012 Code Poems collection as a crossover project.
AI-written summary · about
chapters (11)
- 0:00Introduction to code and art
- 1:25Fundamentals of poetry
- 5:17Parallels between code and text
- 9:34Constraints and sonnets
- 12:55Shakespeare and the Volta
- 17:23The dangers of over-structuring
- 20:00Defining quality in craft
- 23:40Brevity and focus
- 26:46The workshop and feedback
- 30:13The power of revision
- 33:01Conclusion and code poems
related talks
34mShall I Compare Thee to a Line of Code?
36mWhat if Shakespeare Wrote Code?
38mWhat Poetry Workshops Teach Us about Code Review
34mWhat if Shakespeare Wrote Ruby?
08mWriting {{‘poems that change’, ‘chance poems’, ‘dynamic poetry’}}!
36mInfinite State Machine Poetry in, with, and by Clojure
16mThese Songs Would Make Some Great Code Comments
35mCoding: Art or Craft?