essay on codework

[Alan Sondheim]

essay on codework

like every other style, codework will disappear
as soon as it's born, an uncomfortable
miscarriage of the beginning and defensive
tactics of the classic information age. codework
attracts its share of quacks precisely because it
_is_ quackery - and doesn't one ever get tired of
monospacing? but there are more serious
considerations here.:there's no demand for it, no
pleasure in it, it's ult to construct. one would
think that problematic linkages between
programming and literatures would be fruitful,
but the programming is facile, at best
explanatory or obfuscating, and it's already
dated as soon as it's written. you'd have to be
the author to follow it. it's a style that ties
itself into a knot.:there is no transformation,
no knowledge. codework is a fraud. if i could
code, i'd never use the literature fakebook. my
programs are absurd, a few lines at the most. i
can hardly configure a program, much less create
one. codework is last vestige of tradition,
conservative in its subversion of code. it
manages to escape traditional aesthetic
categories in favor of the mess, or knotted
striations. it's dated as soon as it's
written.:the problem with codework:tying oneself
in knots

write first the fake or fraud through my like
every other style, codework will disappear as
soon as it's born, an uncomfortable afterbirth of
the beginning and defensive tactics of the
classic information age. codework attracts its
share of quacks precisely because it _is_
quackery - and doesn't one ever get tired of
monospacing? but there are more serious
considerations here.

monstrous repetition

A sheep and
   fury nightmare
A sheep and
   fury nightmare


__