Library / Music and Dance Practice Engineering Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 09:55:09 UTC

MDPE.20:4.4 - Live coding and Algorave: a label does not forecast a practice

A team sees tools, live-code performances, a manifesto, events, recordings, teaching, and an audience community developing together. It asks whether a local Algorave series will become a continuing practice, merge with another electronic-music scene, remain an event format, or disappear after organizer and venue support ends.

The forecast distinguishes tool accessibility, performer capability, live-performance recognition, event operations, publication, community reproduction, and dependence on named organizers and venues. Observations include independent new performers, repeated events without the original team, transformed but recognizable Methods, audience and curator recognition, and survival under changed tools or venue conditions.

If the question becomes whether these relations constitute a new cultural whole rather than a branch or event format, use MDPE.24. A coined name, manifesto, or successful series alone does not answer either question.