The Alan Sondheim Mail Archive

May 17, 2002


-


film on code/work 5/16/02
foreground: everglades trail @ 190% speedup
background: miami drive @ 200% speedup
sound: mixed from visuals
text-crawl, bottom-screen:
length: 7:24
codework:: f({x}) -> {y} - any mapping is sufficient - TRACE of the
road-vector against the MESS or TANGLE across the glades path.  it
is the arrow - not the terms - that fascinates me - the arrow which
INSISTS on a mapping, linguistic or perceptual. one APPROACHES code
with code; the retina always already encodes, and further coding
provides a bracketing or intersection of terms x^~x permitting
definition. but BETWEEN x and ~x (not-x), there is a chasm or
FISSURE; inscription transforms FISSURE into CLIFF. do you follow
me? I am winging this. in this REALM, everything is inchoate, fuzzy;
one is immersed in the DIALOGIC of FLOWS among schema, scripts,
goals, regimes, mappings, sememes, and configurations. these moments
are THROUGH the path or road, not DOWN. HERE, I have no shadow. THAT
DAY, I was covered in sand-midge, mosquito, and deer-fly bites; I
carried a fever everywhere. but that day I drove the seven miles
brilliantly, reaching my destination in record time. ... ... ... ...
consider a CODE as a MESH with PARASITIC INTENTION. the PARASITE is
the nexus; in the absence of the parasite, all that's left is the
problematic of a 'natural' protocol. it is the PARASITE that
inhabits the sememe; it is the PARASITE that INSCRIBES. think of the
TEE formation: f({x}) <> |P| <> {y}. I inhabit the parasitic; the
road and path penetrate me: I gasp the name of the code: ROAD-NAME
TRAIL-NAME: ***MILLER*** and ***CHRISTIAN POINT***.


_

Generated by Mnemosyne 0.12.