home/ modules/ orientation-electronic-music-lineages

Orientation: how to read an electronic-music family tree

L0Orientation 4h O · Culture, history & theory 14 atoms

Learning objectives

learner can situate house, techno and garage as three parallel early-1980s US scenes and name their cities
learner can explain why four-on-the-floor became the default template and where it breaks
learner can articulate that genres are socially constructed and named retrospectively, often by critics
learner can sketch a one-page lineage map connecting at least six genres by descent

Capstone — one whole task that evidences the objectives

Produce an annotated one-page family tree of electronic dance music from disco to the present, correctly placing house/techno/garage as parallel roots and labelling each edge with the mutation (tempo, rhythm, sampling) that distinguishes parent from child.

When you walk into a record shop, browse a streaming genre page, or hear a live-coder announce “some jungle now,” you are navigating a family tree most listeners never see whole. This module builds exactly that: a one-page annotated map of electronic dance music, from disco’s forced retreat underground to the present, with every parent-child edge labelled by what actually mutated — tempo, rhythm, or sampling. That map is the working mental model behind every genre decision you will make later as a DJ, producer, or live-coder choosing a kick pattern and a BPM.

The arc starts at the root: begin by tracing how the 1979 anti-disco backlash pushed dance music underground and how house was born from that retreat — a supported first exercise is annotating just the disco→house edge. Then widen the trunk using “House, techno, and garage emerged in parallel as three related early-1980s US dance scenes” to place three roots side by side rather than in a false single line. “The four-on-the-floor kick pattern became the dominant rhythmic template” gives you the default edge label, and “The UK hardcore continuum” gives you the counter-lineage where that template breaks into breakbeats — together they supply most of your six-genre descent chain. House’s generativity explains why the tree keeps branching at all. Crucially, two atoms on genre as social construction and retrospective naming keep your annotations honest: the labels on your map were coined by critics after the fact, and your tree should say so.

The required atoms are load-bearing — without any one of them the capstone map has a missing root, a wrong edge, or a naive theory of what a genre label is. The supporting atoms enrich the annotations: lifecycle stages, critic-coined names that stuck, potent clichés, venue-set tempos, and the social infrastructure (record shops, revival nights) that carried scenes between generations.