13 Sep '21
Feedback in livecoding: cui bono?
Hi, BUILD students. I know y’all are busy, so this won’t take too long and will hopefully be fun. Before my guest lecture, I’d like to introduce you (if you haven’t seen it before) to livecoding. Imagine you arrive at the club1, and as well as the glow sticks and the pingers and the heaving bodies on the dance floor instead of a “traditional” DJ you see this:
What can cybernetics teach us about this?
Obviously there are lots of feedback loops in this CPS; involving audience/room/livecoder/screens/lights/loudspeakers etc. But one of the things that interests me most about livecoding is that it gives the club-goers a chance to see (and hopefully to care) about the source code of a computer program.
There’s lots we could say about this from a cybernetics perspective, but the things I want to focus on in this class is feedback.
Here are a few questions for you to think about ahead of class. In each livecoding video:
- what has the performer chosen to show?
- what has the performer chosen to hide?
- who is the feedback for2?
- in each case, why do you think those decisions were made?
- when watching, what did you want more/less/different feedback about?
- if you were the AV designer for Ushini & my next livecoding set, what changes would you make?
- how does a taking a cybernetic approach to this question change answer to these questions? (because feedback is something that cybernetics has a fair bit to say about)
If you want to go a bit deeper on the semiotics of all this livecoding stuff, my collaborators and I have written a couple of papers3 on the semantics/semiotics of livecoding:
by, , and
in LIVE '13: 1st International Workshop on Live Programming at ICSE (pdf)
If there are other thinkers/writers/doers that you can think of who also have something to say about this, then bring those ideas along and we can discuss them as well.