Daily live coding practice builds a fluent repertoire of low-level activities that frees attention for structural thinking during performance

Roberts and Wakefield argue that live coding performance skill develops through sustained, regular practice — not pre-composition and not one-off engineering work. The goal of practice is to build ‘a fluent repertoire of low-level coding activities’ (syntax recall, common idioms, error recovery) so that during performance cognitive resources can be directed toward higher-level structural decisions — where am I going, and what alternative routes exist. This is analogous to instrumental technique: a pianist who must think consciously about fingering has no bandwidth for musical interpretation. Live coding is thus framed as a craft skill grown over time through repetition, not merely a technical skill acquired by reading documentation.

Examples

Daily practice of common Tidal patterns (bd, sn, polymeter, every, jux) until they become automatic. This frees the performer to focus on macro-structure (when to drop elements, when to introduce new sounds) during an algorave set.

Assessment

Describe the role of daily practice in developing live coding performance skill. What specific aspects of live coding benefit most from automatization through practice?