Flashing each pattern element as it becomes active gives a live coder direct visual feedback on timing

A live-coding editor can show the running state of a pattern by flashing each syntactic element at the moment it becomes active. McLean’s FeedForward editor does this: as the pattern plays, the on-screen token for the currently sounding event lights up, plus VU meters. This closes the gap between the static text and the time-varying sound — the coder can see where the cursor’s edit will land relative to the beat, rather than inferring it by ear alone. It is an instance of a general principle: because live-coded notation is ‘one step removed’ from the sound, tightening the visual feedback loop between code and output helps the performer align new edits to the running material. The idea originated for teaching eight-year-olds, where immediate visual feedback matters most.

Examples

In FeedForward, the bd token flashes each time the kick fires and a VU meter moves with the level, so a coder editing mid-cycle can time an insertion to the next flash rather than guessing.

Assessment

Explain how per-element flash feedback in a live-coding editor mitigates the ‘map is not the territory’ gap. What does the flash tell the coder that the static text does not?