In live coding an error is material to work with, not a failure to hide

A guiding stance in live coding is that errors and unexpected results are not failures but new material. Sam Aaron’s Sonic Pi philosophy states there are ‘really no mistakes’ — the productive response to a wrong-sounding result is to manipulate it (change an option, add an effect, transpose) and morph it into something interesting rather than stopping, a mindset borrowed from jazz improvisation. The same principle has structural, not merely motivational, support: because live-coded errors are visible to the audience, they can be reframed as part of the performance rather than hidden defects, so the fear of error no longer blocks experimentation. Lucy Cheesman traces this pedagogy to a 2015 all-women workshop by Joanne Armitage and Shelly Knotts, who told participants to embrace error; removing the pressure to be accurate creates space to experiment. Armitage argues underrepresented groups especially need a safe space to fail constructively — contrasting with mainstream computing culture, where error is treated as shameful.

Examples

At an algorave, a performer evaluates code that throws an error: the sound stops momentarily, the audience sees the error message, the performer fixes it and continues — the crowd may cheer. This spectator moment is impossible in pre-recorded performance. In Sonic Pi, when a live_loop riff sounds wrong: change one opt, add FX, or transpose — don’t stop.

Assessment

Describe a scenario where an unexpected sound in a live_loop is turned into a feature rather than corrected, and explain why this matters specifically in live performance. Then explain why embracing error has structural support in the live coding format itself: what feature makes an error a spectator event rather than a hidden failure?