Live coding is improvisation with a map that generates the territory: you cannot read the code until you run it

Alex McLean describes live coding through Korzybski’s maxim: ‘the map is not the territory.’ In live coding, the code is the map and the sound or visual output is the territory. Unlike playing a drum, where the action and sound are simultaneous, the live coder writes a description that generates something, then must listen to that output to understand what they have written. The code cannot be read in isolation — it only acquires meaning once enacted. This one-step-removed relationship creates the possibility for surprise: a small change in the code can cascade through a compositional system to produce effects beyond the programmer’s expectation. Surprise is McLean’s criterion for what distinguishes live coding from mere notation entry.

Examples

You write a one-line TidalCycles pattern, press evaluate, and hear a polyrhythm you did not consciously design. You modify one function and the texture shifts unexpectedly. The sound tells you what the code meant.

Assessment

Explain in your own words why McLean considers surprise a necessary criterion for live coding. What is the difference between a live coder and someone ‘transcribing an idea from their head’?