home/ modules/ practising-to-get-good-at-live-coding

Practising to get good: mindset, peers, and learning from expert patches

L1Foundations 4h P · Community, scenes & practice 6 atoms

Learning objectives

learner can name the real obstacles to improving — habits and mindset over the code itself — and set up practice habits accordingly
learner can use social learning accelerants: a similar-level peer sparring partner, sharing work publicly early for feedback and accountability, and dissecting expert patches with the designer's commentary to capture the tacit 'why'

Capstone — one whole task that evidences the objectives

Design and commit to a four-week personal practice regimen for live coding: name a peer sparring partner and cadence, a public-sharing schedule, one expert patch to dissect (with the questions you'll ask of its commentary), and a mindset habit you're targeting — then run week one and write a short reflection.

Prerequisite modules

Orienting in the live-coding world: TOPLAP, algorave, and the map of the scene

The whole task here is not a performance — it is designing the practice life that makes performances possible. Live coding punishes sporadic effort: an algorave set, a SuperCollider patch, a TidalCycles groove all demand fluency that only accumulates through weekly, structured reps. This module has you build and actually start a four-week regimen, because most beginners stall not on syntax but on the absence of a sustainable routine.

The scaffolding arc starts with diagnosis: the principle that habits and mindset, not the code itself, are the main obstacles reframes what you are even practising. From there you assemble the social machinery — the atom on peer sparring partners tells you why “similar level” is the criterion that matters when you name your partner, and the atom on sharing work publicly early answers the inevitable “but it’s not good enough yet” objection when you set your sharing schedule. The patch-dissection method atom then guides the most technical element: choosing one expert patch and writing the “why is that there?” questions you’ll put to the designer’s commentary. Week one runs supported by these pointers; the closing reflection is unsupported — you articulate, in your own words, what worked, what didn’t, and what you will change for weeks two to four.

Each required atom gates a named component of the regimen: drop any one and that slot in the capstone goes hollow. Two supporting facts enrich the mindset story without gating any deliverable: the first live coders emerged from art schools, not CS departments — your lineage is creative practice, and it licenses treating code as craft material rather than an exam to pass — and music has long served as a naturally motivating context for learning to think in step-by-step processes, which is exactly the disposition your regimen is training.