In the spirit of dogfooding I personally have built an endless number of half-finished systems that I abandoned before using due to changing requirements, environments and technical contexts. I’ve learnt and lost and relearnt a lot of specific technical knowledge in these processes, and wasted a lot of time. I still love to half-build things; I respect the process, and am considering how to document partial practise. I’m currently enjoying the notion of ‘provotypes’ (Smolicki, 2017), a term I identify in my practise of designing/building half-complete prototypes as a learning exercise. The artifact is either abandoned or remixed or iterated later on, but the process and insights have ongoing use and impact of ‘provoking’ insight.

experimental publishing as collective struggle

why live docs are resistive
why commons are resistive
why assemblages are resistive
remix culture in relation to scrapbooking

internet economies

no preview

code self-exemplifies and self-documents

also self-archives, eg version control
can self-reflect

“The programmed artifact hence becomes simultaneously a residue, or a record of steps taken along the way, while obviously acquiring its intended function of a repository and structuring device for organization and display of digitized content.” ⤴️