Live coding performances arc from empty to complex and back to silence, suggesting cyclic rather than linear revision control

Conventional software development is linear: from nothing to a finished shipped product. Live coding inverts this: both beginning and end are empty (blank editor, silence). The creative arc is a cycle. McLean proposes that revision control systems should be redesigned to support cyclic development — helping performers return to prior states for musical reprise, not just move forward toward milestones. This connects to musical concepts of theme and variation, and to Buzsaki’s distinction between linear time (pantha rei) and cyclic time (circle of life).

Examples

A live coding set: blank editor → simple kick → layered polyrhythm → timbral complexity → strip back → silence. Conventional git: commit history moves only forward. Proposed cyclic revision control: snapshot states for musical reprise.

Assessment

Explain why the conventional linear model of revision control (git) is misaligned with live coders’ artistic needs. Propose one concrete feature a cyclic revision control system would require, and identify which musical structure it would support.