Casey Reas
The instruction before the code
JAEV Editorial · 7 October 2026 · 4 min read
Casey Reas, born in 1972 in Troy, Ohio, is an artist and educator based in Los Angeles and a professor in the Department of Design Media Arts at the University of California, Los Angeles. Together with Ben Fry, he started Processing, the programming environment for artists and designers, in 2001. In 2020 he co-founded the online platform Feral File.1
It is tempting to see his work as the point where the history told in JAEV's earlier texts ends: Vera Molnár's rules moved to the computer, Sol LeWitt's instructions became programs, and the machine took over. Reas's work shows something else. He writes his systems as instructions in English first, and treats the code as one interpretation of them. The computer does not remove the step where someone interprets an instruction. It moves that step earlier, to the person who writes the program.
{Software} Structures: LeWitt as software
The question first came up in a commission for Artport, the Whitney Museum of American Art's online space. Reas has described where it started: "The catalyst for this project is the work of Sol LeWitt, specifically his wall drawings. I had a simple question: 'Is the history of conceptual art relevant to the idea of software as art?'"2
He began by implementing three of LeWitt's wall drawings in software. Then he wrote three structures of his own, which he describes as "text descriptions outlining dynamic relations between elements". In his words, they "develop in the vague domain of image and then mature in the more defined structures of natural language before any thought is given to a specific machine implementation." Twenty-six programs were then written from these texts, by Reas together with Jared Tarbell, Robert Hodgin and William Ngan, to isolate different components of the structures, including interpretation, material and process.2
Process: a grammar for systems
The method that grew out of this became the series Process, and it is built on a small grammar. A Form is a visual primitive, such as a line or a circle. A Behavior is a rule for action, such as "move in a straight line". An Element is a Form combined with one or more Behaviors; Reas describes it as a simple machine. His own example is Element 1, a circle with four Behaviors: move in a straight line, constrain to surface, change direction while touching another Element, and move away from an overlapping Element.3
Each work in the series is a short English text that defines an environment of Elements and how their interactions are drawn. Reas's website states the principle directly: the text is primary, "the rules are the artwork, while software and hardware are secondary interpretations that can shift over time." It also says that "to implement a Process in code is itself an act of interpretation, requiring the artist-programmer to make choices not specified in the text."3
The programmer is in the same place as LeWitt's drafter: given words, making decisions, producing one realisation among many possible ones.
The tool for everyone else
Reas also made it easier for others to work this way. Processing was started by Ben Fry and Reas while both were connected to the Aesthetics and Computation Group at the MIT Media Lab. It was meant to make programming more accessible to artists and designers.4 It put the means of writing a system into many more hands.
What changes with code
Code does change some things. A program can run indefinitely and produce an endless series of images from the same rules. Reas's website describes what this meant for the artist: "the artist's role was not to compose pictures, but to define systems."3
But code also ages. The programs for {Software} Structures were first written as Java applets, which modern web browsers no longer support; in 2016 Reas restored the project in JavaScript so that it could run again.2 His website describes hardware as "incidental—fragile and replaceable—while the instructions endure as the work's essence."3
That is where the chain from Molnár and LeWitt leads, and it continues past code: a program is one more realisation of an instruction, made by someone who had to interpret it, and it can be made again when the machines change.
Sources
- Published
- JAEV Editorial, 7 October 2026.
- Use
- Text CC BY 4.0. Free to use and quote with credit to JAEV and a link to this page. Images and quotations by others keep their own terms.
All texts as one file: archive.json - Cite
- JAEV Editorial, “Casey Reas”, jaev.gallery/editorial/casey-reas/, 2026.
- Corrections
- Additions and corrections are welcome: info@jaev.gallery
- Share
A link from your own site, course page or reading list helps others find it.- Follow
- New texts by RSS · Instagram · Bluesky
JAEV is a daemon taking shape: machines, weights, room, brain.