PROGRAMMER MUSIC

Notes Toward a Music of Sequences, Cheap Machines, Ghost Signals, and Unapproved Methods

A programmer once meant somebody who arranged movies.

Not necessarily the director, not necessarily the producer, and certainly not the person whose face appeared twenty feet high over the theater entrance. The programmer assembled the evening. A western, a crime picture, a newsreel, a cartoon, another feature. Cheap films, old films, strange films, whatever could be obtained and made to work tosgether for an audience sitting in the dark.

A programmer now also means somebody who writes instructions for a machine.

These meanings have become accidentally useful to me.

Programmer Music sits somewhere between them.

It is music made through selection, sequencing, interruption, repetition, corruption, recombination and transmission. It may contain guitar, code, radio, MIDI, found sound, generated sound, damaged sound, samples, homemade recordings, synthetic instruments or things whose origins have become difficult to determine.

The important thing is not the equipment.

The important thing is the program.

I have spent more than twenty-five years making things with whatever was available: instruments, cheap recording equipment, homemade artwork, consumer electronics, computers, photocopies, websites, books, bad speakers, good accidents.

The tools change. The impulse does not.

Recently that toolbox has included AI.

This has produced objections.

One Reddit commenter offered perhaps the most economical review Outer Order has received:

“Holy AI slop, what a bunch of noise.”

Fair enough.

I upvoted it.

More importantly, I looked at the commenter’s own work and found something I genuinely liked: real-time ASCII graphics, Raspberry Pi experimentation, the kind of hands-on technical curiosity I recognize immediately even when the person practicing it has arrived at very different conclusions about my work.

That matters more to me than winning an argument.

The comment also accidentally identified something real.

It is a bunch of noise.

Noise from radios.
Noise from guitars.
Noise from obsolete media.
Noise created intentionally by algorithms.
Noise created unintentionally by imperfect systems.
Noise transmitted across decades and stripped of its original context.

The question is what happens when somebody programs that noise.

For me, AI is propulsion, not source.

The source is the accumulated mess behind it: records heard at the wrong age, cheap stereos repaired incorrectly, late-night movies, punk flyers, jazz records, horror hosts, public-access television, photocopied zines, RadioShack electronics, science fiction, broken media, East Coast basements, books, conversations, decades of making things because making things was available even when money was not.

AI does not replace that history.

It collides with it.

So does Python.

So does a guitar.

So does a shortwave recording.

The distinction between “traditional” and “technological” art becomes particularly strange when you remember that recorded music has always been technological. Microphones altered performance. Tape altered time. Multitracking allowed musicians to accompany versions of themselves who no longer existed. Synthesizers turned voltage into orchestration. Sampling turned recordings into instruments. Digital editing made the waveform itself editable material.

Programmer Music simply admits the machinery is there.

It does not ask the machinery to disappear behind an illusion of purity.

That is why radio transmissions have become so important in this work.

In “An Accusation,” voices and signals that seem to arrive from another era enter music constructed by contemporary computational means. They are not there merely because old radio sounds spooky.

They represent transmission.

A human voice becomes electricity, becomes signal, becomes noise, becomes archive, becomes file, becomes material, becomes music.

Someone speaks.

A machine carries it.

Another machine preserves it.

Decades pass.

Another machine interprets it.

Then someone presses play.

That chain interests me enormously.

And it brings us back to the other kind of programmer.

Imagine the person assembling a neighborhood movie bill eighty years ago.

They have limited resources. They cannot manufacture a new Humphrey Bogart picture because Tuesday night needs one. They work with what exists.

So perhaps they put a crime film beside a horror picture beside a newsreel.

Suddenly those separate objects begin commenting on one another.

Sequence creates meaning.

That is programming.

A coder knows this.

A DJ knows this.

A mixtape maker knows this.

A film programmer knows this.

A musician arranging an album knows this.

A kid placing two completely inappropriate songs next to each other and discovering that the collision creates a third emotional state knows this.

Programmer Music begins there.

It treats composition partly as the creation of individual sounds and partly as the construction of systems in which sounds can encounter one another.

Sometimes I write the guitar.

Sometimes I write the rules that produce the environment the guitar enters.

Sometimes I deliberately surrender control over a small element because the surprise produced by the system is more interesting than something I would have consciously chosen.

Then I intervene again.

Human.

Machine.

Human.

Machine.

Not competition.

Feedback loop.

The result will sometimes be ugly.

Good.

Sometimes excessive.

Good.

Sometimes an algorithm will produce something useless.

Delete it.

Sometimes it will produce something you would never have conceived consciously.

Keep it.

Taste remains necessary.

Editing remains necessary.

Judgment remains necessary.

The programmer is not absolved because the program ran.

That may actually be the central principle.

The machine can generate possibilities. The human still has to mean something.

This is why I am comfortable calling what I do Programmer Music.

Not because I have abandoned instruments for computers.

Not because code has replaced composition.

And certainly not because I think technology automatically makes art interesting.

I use the term because programming describes a way I have approached culture for most of my life.

Take available materials.

Understand the machinery as well as you can.

Misunderstand it productively when necessary.

Arrange things that were not supposed to touch.

Run the system.

Listen.

Change something.

Run it again.

Eventually the machine produces something that surprises its operator.

That moment is not the end of authorship.

That is where authorship gets interesting.

Somebody on Reddit may call it AI slop.

Somebody else may call it experimental music.

Someone may call it coding.

Someone may call it collage.

Someone may ask why a radio announcer apparently trapped in 1943 has suddenly materialized inside a piece of computer-generated music while a guitar howls somewhere behind him.

My answer is increasingly simple.

Programmer Music.

Two definitions.

One method.

A bunch of noise.

Programmed.