How to destroy your work (and why you should)
summary
Rapid prototyping leads to concrete claims and failures: a cardboard-first prototype turns into a carpentered scribbler animatronic pencil that prints tweets, an Arduino blows when fed the wrong voltage, and the install collects about 800 legit messages (plus many ASCII penises). Live‑coding rigs use Cyril, Sonic Pi and LiveCodeLab, pipe FFT audio into visuals, capture HD screenshots every two seconds to make prints, and intentionally discard most code and hardware when a better idea or broken part appears.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:02Why I program
- 5:16Short projects and new project smell
- 6:41Game jams and rapid prototyping
- 7:43Corner House gallery and sketches
- 10:07Building Scribbler machine
- 13:57Prototyping giant pencil
- 14:39Destroying work and change
- 15:42Scribbler machine demo
- 18:40Live coding demo
- 20:04Live coding vs regular programming
- 21:51Live coding manifesto
- 23:22Live coding in unpredictable environments
- 26:34Live coding with web data
- 27:38Why live coding feels terrifying
- 28:43Live coding tools
- 30:51Live coding environments
- 33:38Live coding techniques
- 35:07Destroying work and forward motion
- 35:50Q&A
