Another way of looking at the "breakpoint" version is as a relay event,
where person 1 builds up a code base, passes over to person 2 who
deconstructs it down to a minimal amount, passes to person 3 who builds up,
etc.... Events could include 4x4 mixed medley - and other swimming
metaphors. Live coding team sports : )
Cheers,
Andrew B
On 3/9/07 3:18 AM, "Nick Collins" <nc272_at_cam.ac.uk> wrote:
> here's a little something which Andrew, Andrew and I were discussing over
> dinner this week.
>
> Rather than starting from a blank slate, you could begin with as much code
> as you're ever going to write. Then your task is to gradually delete
> instructions (like a game of jenga?). Perhaps you'd deconstruct, perhaps
> you'd destroy and subvert. But you might end the set by deleting the last
> consequential command and thus bring visualisation, audio or vibrotactile
> olfactoriness to an end.
>
> This can of course dovetail with blank slate coding, indeed, the two can go
> in waves. Perhaps a timer controls the process and participants first build
> up, then down, swapping the hot seat.
>
> A breakpoint envelope/control function might determine swap times and
> changes being creation and destruction. A up B down, B up, A down might
> form one variant. And so forth...
>
> Plus, all the participants would wear waistcoats and stroke their chins as
> their opponent moved matters to tricky positions.
>
>
>
>
>
>
>
Received on Tue Sep 04 2007 - 12:47:05 BST