> Perturb your algorithms mid-flow!
perturb them though not by the inlets, but perturb that which has defined them
a bit like: change not the turing-tape but the turing-head! And conveniently, for a reasonably universal machine, we can use the tape for that.
> On 31.12.2015, at 01:45, alex <alex_at_slab.org> wrote:
>
> On 31 December 2015 at 00:33, Rob Myers <rob_at_robmyers.org> wrote:
>> On 30/12/15 03:48 PM, Amy Alexander wrote:
>>> How about "live coding is performative coding" as a way of thinking/talking
>>> about it? Not necessarily in the sense of stage performance, but in the
>>> sense of performative speech
>>
>> Yes I think that's excellent, IMO it's ideal in terms of direction and
>> generality.
>
> It's a bit strange though, because the 'code' bit implies you don't
> know what it does until you run it.. So it's like performing actions
> with utterances where you don't know exactly what actions you're
> making until you've finished speaking. This is my general experience
> of trying to get people to do things anyway.
If I correctly understand performativity as it is mostly used in the humanities today, it doesn’t assume predictive knowledge of the outcome of the action. Usually quite the opposite, it claims we cannot know without doing. But again, this is why the “classical” performative aspects of utterances are part of their semantics, which is shared. Also, other computational processes have been described as performative in the above sense, in that they require an execution to be what they are.
If we want to explain to fellow computer scientists what live coding is, this term may not help much though, I fear (Amy, have you had other experiences?). In those cases, it is helpful to distinguish between processes that require refactoring to function correctly and those which don’t. Live code requires refactoring at runtime to work.
By consequence, live coding systems must be structured in a way that their programs can function in a constantly preliminary, partial, or incomplete state.
Well at least this would be a final description of the non-final.
--
Read the whole topic here: livecode:
http://lurk.org/r/topic/24WenjS1Hl8Upw4pmozfmX
To leave livecode, email livecode_at_group.lurk.org with the following email subject: unsubscribe
Received on Thu Jan 07 2016 - 16:14:25 GMT