Just as writing in the second person amplifies the contexts for language's reuse, reinterpreting pages that move freely between contexts of collaboration as 'hares' evokes art historical allegory in the presentation of sequences of content:
> At the beginning of the performance Beuys locked the gallery doors from the inside, leaving the gallery-goers outside. They could observe the scene within only through the windows. With his head entirely coated in honey and gold leaf, he began to explain pictures to a dead hare. Whispering to the dead animal on his arm in an apparent dialog, he processed through the exhibit from artwork to artwork. Occasionally he would stop and return to the center of the gallery, where he stepped over a dead fir tree that lay on the floor.[2] After three hours the public was let into the room. Beuys sat upon a stool in the entrance area with the hare on his arm and his back to the onlookers.
XP and Agile are dual strand principles of production that, when applied, enable collaboration between programmers working in an open-source capacity. This entails treating the ethical as a relation of production, perhaps distinct from the means of production: notions such as Build for Today Design for Tomorrow, Do the Simplest Thing that Could Possibly Work and Once and Only Once are precepts that, when applied, endow any multifaceted creative process with purpose.
How to Explain Pictures to a Dead Hare (1967) is Joseph Beuys' best-known art action. I've always thought this piece was pretty weird. But not as weird as what we point to in computer science in order to interpret value:
>In computer science, a pointer is an object in many programming languages that stores a memory address. This can be that of another value located in computer memory, or in some cases, that of memory-mapped computer hardware. A pointer references a location in memory, and obtaining the value stored at that location is known as dereferencing the pointer. As an analogy, a page number in a book's index could be considered a pointer to the corresponding page; dereferencing such a pointer would be done by flipping to the page with the given page number and reading the text found on that page.
Pages are computational memory images that interpret pictures through the use of various data and new media plugins.
The week following the UCLA (instead of jumping into more applications in the season of nepotism) application, I built the site I submitted to UCLA out as a template.
By approaching the process as a (real) college application and completing the essays and portfolio sections in a personal way first, I was able to action out a separation of concerns. Federated wiki furthers the closure of the copy-edit loop, meaning:
Traditional publishing: Draft ➨ Review ➨ Publish
Federated Wiki: Publish ➨ Review ➨ Fork ➨ Draft ➨ Publish ➨ Review
Normally when we share online, our content doesn't *get better* the more 'likes' or 'shares' it receives. On Federated Wiki, the opposite is true.
For example, in the course of creating a template for a grad school app, a stranger from Germany noticed my attempts to make the art work I'd produced for an arguably narrow capacity in the New York City culture industry relevant to People Projects and Patterns in software development.
But it was by accident, thru 'surfing' pages, clicking links that led from one link to another, that I discovered Ralf Barkow had been forking my pages and refactoring page content to include other perspectives. I could then fork these pages back and continue writing on them to elaborate my ideas in the directions a new collaborator had outlined.
By making the site reusable over the course of a development week following having submitted the application by deadline, I abided a separation of concerns that would have confused the very personal process of applying to graduate school with the experimental deconstruction of the application through an applied use of software.
Lineup Diagram changes based on where you've clicked. Draw here for a sitemap, then search for 'Lineup Diagram' to compare paths through the model.
And each page contains a record of action: attribution is automatic using CC-BY-SA 4.0 creative commons licensing. This is a record of ownership and also a reason to write in the second person.