Live coding lacks the DJ's ability to preview material before presenting it, so submitted code goes straight to the audience

Roberts and Wakefield identify a structural difference between live coding and DJing: DJs mitigate performance risk by previewing — auditioning tracks or loops on headphone cue before committing them to the mix. Few live coding environments support this; code typically executes straight to the audience with no private audio preview. Temporal pressure (coding is more intensive than track selection) and the risk of reducing variation both discourage patient previewing. Even deterministic algorithms can produce unexpected sounds, so a coder cannot fully anticipate output from the source alone. Ensemble setups partially restore previewing: with a central machine projecting output, each performer can audition code on their own laptop’s audio before submitting it — provided the code does not depend on the central machine’s state.

Examples

A DJ cues the next track in headphones before crossfading. A solo TidalCycles performer has no equivalent: evaluating a pattern sends it live. In a networked ensemble, a performer runs a pattern locally to hear it, then submits it to the shared central instance.

Assessment

Explain why previewing is harder in live coding than in DJing, and describe one ensemble arrangement that lets a live coder preview code before it reaches the audience. What constraint limits when that arrangement works?