An actionable definition of : computer program

An actionable definition of : computer program

The experience a user gets when interacting with a machine called a computer, created by controlling how a computer behaves in response to stimulus (called input) from a user, or by controlling how a user responses to the perceived characteristics of the computer's behavior.

It just struck me that there is so little difference between a computer program and music. That the only time you cannot deny it is a program is when someone is running it. That the source code can no more be the program as can music be heard on a manuscript. That while the process of creating the program may be in isolation, the user is part of the program as much as the listener is part of the music. That programs rarely exist in vacuum but run in an environment full of things such as process scheduling priorities, third party libraries, logic implemented in hardware, just as music is rarely heard in the absolute silence of sounds and personal histories.

The term "user interface" used to mean the pictures on the screen designed by designers for real programmers to follow. Now it's called "user experience" but programmers still think its secondary. So let me say it: the experience IS the program.

Certainly, "real" programs doing heavy duty computing for highly intelligent professionals don't "need" a pretty interface. But whatever "ugly" interface preferred by these users, is perfect only because it is in harmony with the tone of the user'a behavior - just as not all music need words or harmony or melodies.

This brings me to propose that there is a 4:33 of computer programs - shutdown.exe. It is the ultimate expression of what a program can be: the experience of a program can extend beyond the runtime of the program. Shutdown.exe demands a response from its user like no other program does. Sitting through a whole four minutes of it, is like a form of anti-meditation - you can't really sit down and focus on experiencing it.

It is a sad thing that few will get to appreciate the deep conversations between the user and the computer in the 4:33 of programs. Even more so that many platforms are removing the idea of shutdown from the user's universe completely. In a way it's
like claiming that 4:33 isn't music.

There is a host of reasons why well meaning people are in the business of removing shutdown.exe - but it is comforting that reality is currently winning; shutdown.exe has largely been upgraded to demand-reboot-after-updating-while-you're-halfway-through-your-essay.exe. Sure, there is a reality out there where shutdown.exe completely does not exist, but for now, before you say fuck to that annoying pop up the next time - treasure it while it lasts.