Live coding and algorave: showing the screen

Live coding matters in this module not as a software discipline but as a performance culture: you are learning to stand in front of a dancefloor, project your running code, and defend every aesthetic choice as your own — not the algorithm’s. The capstone makes that concrete: a written artist statement / program-note for a hypothetical algorave set. Getting that statement right requires fluency in the scene’s core vocabulary and values, which is what the required atoms deliver.

The scaffolding arc begins with identity and lineage. The two misconception atoms on live coders versus DJs build the definitional floor — without them a performer can’t explain their practice to an audience member in thirty seconds, which is a realistic performance demand. The rave-law parody definition of algorave and the dancefloor-focus principle sharpen what kind of music is appropriate: functional for dancing, not merely algorithmically interesting. The live-electronics lineage atom and the generative-rave lineage from Eno through Autechre give the artist statement its historical anchor — objective four of the module requires this situating, and the capstone cannot be written credibly without it.

The show-your-screen atom, TOPLAP community atom, open-collective model, and folk-music model together cover the ethical dimension the artist statement must articulate. The folk-music framing supplies the vocabulary for explaining why code is shared and borrowed rather than owned — essential for the “open-collective and folk-music values” clause of the capstone prompt.

Supporting atoms enrich without being gated: the tool-ecosystem overview, the hacker-geek-club triangulation, and the historical humility principle deepen a performer’s worldview and sharpen Q&A responses, but a learner who has mastered the required set can already complete the capstone without them.