kamo
/
kamo-soupbato
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

final

Browse Source
master
km0 11 months ago
parent 5e7a9223c2
commit 052dfd2205
4 changed files with 282 additions and 1 deletions
Show Stats Download Patch File Download Diff File

63
contents/ass.md
Unescape Escape View File

@ -0,0 +1,63 @@
A list of things made in these two years at xpub
- a spreadsheet to chat converter
- a web design 101 workshop
- a bookmarking tool for pads
- a tool to annotate images
- a tool to annotate images together
- the documentation website for a vernacular api
- a tool to stick HTML sticker on webpages
- a prototype to publish 100 puzzles with 100 pieces each, but shuffled
- a git-to-web-to-print system to print 80000 post-it
- a cms for modular synth patches
- a system to navigate web pages drawing virtual cables
- a framework to generate interactive synth panel from svg files
- a small sequencer inspired by tidal mini notation
- a playlist that is a map that is an instrument to perform an opera piece
- a multi-author web-to-print libretto for an emerging opera
- a small shared snapshots archive, to keep track of the evolution of projects
- a branching version of exquisite corpse (drawings)
- a guide on how to interact with the mediawiki api
- a tool to cut pdfs
- a writing machine to organize text by tags
- an interactive birthday card
- a cms for birthdays
- a tool to weave together different texts with different patterns
- a git-to-web publishing system
- a flat markup language
- a shared single file CMS to document projects
- a csv-to-midi sequencer
- a subtitle oriented web timeline
- a collaborative and multi-output real-time drawing app
- a series of activities concerning code documentation
- some experiment with web audio api
- a git-to-web-to-print system for writing the thesis
- a thesis
- a publishing house focused on republishing and amazing cover with animals
- some ascii art animations
- a tool to list all the PZI wiki pages
- a branching version of exquisite corpse (writings)
- a concert in varia
- a word-based drum machine
- a percussions piece made in the park with water bottles
- a lot of live coded jingles for weekly audio pubblications
- some documentation workout
- experiments concerning code documentation
- started using vim
- an app to sketch storyboards
- another bookmarking tool (with a lot of new functions!)
- 3d printed legs to make your server run 4x times faster
- a writing machine to tinker with the list format
- a hand drawn videomapping + css live coding tool
- a website you can visit just once
- a lot of readme files
- a lot of cover for those readmes
- a system to update the wiki from our server
- a rolling fanfiction about katamari
- some versioned essays
- different cmss
- different frontends
- different backends
- some glue for a collective api
- a karaoke republishing tool (record and replay your text on your midi!!)
- a cms for soups

123
contents/final.md
Unescape Escape View File

@ -0,0 +1,123 @@
In this presentation i will look at the work made across the 2 years to reflect on how it changed my understanding of code documentation.
Code documentation intended as a rich set of practices: comments in code, readme files, tutorials, guides, references etc., but also moments of collective learning, workshops, pair programming and collaborative documenting
These aspects are usually marginal in software development: byproducts surroinding the real thing, extra and treats not always available in the scarce economies around documentation.
I would like to focus on these marginal zones, bring them to the center and explore how do they influence practices of programming & sociality around software development.
The required awesome list of things done during these two years is left in the background.
<!-- AAAAH i can put it as a blurred background ahaha amazing -->
## your thesis (only a brief overview for context, as this has been assessed separately in depth),
Excerpts from [Hello Worlding: code documentation as entry point / backdoor to programming practices](https://hub.xpub.nl/soupboat/~kamo/thesis/)
> Code documentation is an ideal publishing surface to create worlds around software, and to orientate software in the world.
> The nature of code documentation is to create entry points for people to participate in programming practices. To encode and filter knowledge, and ultimately to share it with others. This "nature", however, does not come without issues. It makes a lot of assumptions about who's reading, expecting experts, or engineers, or dudes. Its language is unwelcoming: too dense, too technical, very gendered and unable to address anyone but the neurotypical-white-cis-male programmer. Documentation requires an enormous amount of care, energy and time to be maintained, and it's done always out of budget, always as a side project, always at the end, and only if there's time left.
> Even if it does a questionable job at creating entry points, code documentation still has a lot of potential as a backdoor. It's a publishing surface whose reach extends through time and space. Time because it meets programmers at different moments in their lives: from the _hello world_ till the _how to uninstall_, and it influences thinking about software continuously, and from different perspectives. Space because it comes in many different possible formats, and can shapeshift to serve different occasions: from simple .txt files to entire websites, from coding workshops to comments in the source code to series of video tutorial. The question then becomes: can we make use of these backdoors to infiltrate programming practices and open more entry points from within?
> I started this research for of two reasons. The first is that I love programming because is like learning another language: not just a new bag of words and a different grammar, but a whole new way of thinking, a lens through which to look at the world. Coding means to express ideas with the reduced vocabulary of a programming language. As in poetry, these constraints stimulate creativity, and encourage a diligent yet playful approach. Working with different programming languages and on different systems transforms thinking in multivarious ways, and that is extremely exciting.
> The second reason is that I want to share this excitement with others, especially with my friends. To be able to think and make sense together of what's happening around us, and come up with alternatives or responses or tools that suit us better. Because of the steep learning curve of programming and the other barriers previously mentioned, this has often not been possible. But now we know that there are other ways in, and that it is possible to open up even more.
## your individual contributions to the special issues,
Ahah what do we even mean by _"individual"_?
Note that every special issue is a wild ecosystem of things happening at the same time: some of them have the brief lifespan of a cactus flower, some of them reach the public, some others remain in the background, some are subtle gestures, some crazy dangerous proposal.
Some info for context:
- came to xpub with some experience in programming
- a brain wobbled for years between interaction design and contemporary art & web development and design for super corporate clients
- for the sake of working together with others coming from different fields decided to leave a bit aside super tech specific frameworks and languages i was familiar with and return to more accessible things
- (vanilla js instead of vue for example)
- (from windows-only vvvv to a more cross platform platforms such as browser or python)
### SI16
A group of art students tries to familiarize and handle the concept of API, to use it as a publishing surface.
Code documentation
- as personal understanding of an unknown and complex concept
- chae's drawings
- miri's meme
- grgr & sumo diagrams
- as shared struggle
- tone of voice in code comment screaming for help
- sessions of pair programming to face technical stress
- as collective practice
- multi voiced through jupiter notebook
### SI17
a group of art students tries to print 80 000 post-its and put them in 100 loot boxes
Code documentation
- as facilitation to distributed authorship
- post-it generator, git as cms
- as poetic and political writing
- comments in the screenless office
- queer motto api readme
### SI18
a group of art students releases 8 weekly sound+ publications alternating roles of curation and contents production
code documentation
- as invitation for particular workflows
- as starting point for further explorations (kiwiboat)
## the development of your reading/writing practice across the 2 years,
reading
1
versioning: search & replace terms in essay to talk about something else
API as worldbuilding (graphic design => api)
murderous history of lootboxes (mimic => lootbox)
2
get to know that something like software studies exist!
and it's amazing because software is my passion tm
birds press, active reading, reading as republishing
writing
dev a lot of small writing machines to write in different ways
dlist wlist tag pathways soupboat/~kamo
readme files and comment in code
thesis
## the development of your prototyping practice across the 2 years,
software development is my passion
what i like is: developing tools for others to use
explorations outside the computer:
birds press and different printing and bookbinding techniques
3d printing for soupboat and project
## your final work and research in the second year,
problematize code documentation practices
organized some worshop and small social gatherings around code development
printed some zines
printed some stickers
writing a lot of readme in many different ways
## plans for final publication and grad show (with the understanding that you will continue to work on this after the assessment)

9
flask_boat.py
Unescape Escape View File

@ -115,6 +115,13 @@ def dynamic_page(slug=None):
return render_template("page.html", **meta, content=content)
@app.route("/pres/")
def pres():
meta, content = get_md_contents('final.md')
_, awesome_list = get_md_contents('ass.md')
return render_template("final.html", **meta, content=content, list=awesome_list)
# Single project
@app.route("/projects/<project>/")
def p_info(project=None):
@ -156,4 +163,4 @@ def render():
# RUN
app.run(port="3132")
app.run(port="3132", debug=True)

88
templates/final.html
Unescape Escape View File

@ -0,0 +1,88 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>my 2 cents about code documentation</title>
<style>
body {
background-color: dodgerblue;
font-family: sans-serif;
}
.list {
position: absolute;
top: 0;
left: 0;
padding: 32px;
padding-left: 64px;
font-family: serif;
font-size: 96px;
color: white;
filter: blur(10px);
transform: translate(10px);
transition: all 0.2s ease-out;
}
.list:hover {
filter: blur(1px);
transform: translate(0);
transition: all 1s ease-in;
}
.list ul {
list-style: none;
list-style-type: "- ";
list-style-position: outside;
}
.list li + li {
margin-top: 0.4em;
}
.contents {
position: relative;
z-index: 50;
margin: 32px auto;
font-size: 42px;
max-width: 60ch;
filter: blur(10px);
transform: translate(100px);
opacity: 0.5;
line-height: 1.6;
transition: all 0.6s ease-out;
}
.contents:hover {
transition: all 0.4s ease-in;
filter: blur(0px);
opacity: 1;
transform: translate(0);
}
a {
color: white;
}
</style>
</head>
<body>
<main>
<section class="list">{{list|safe}}</section>
<section class="contents">{{content|safe}}</section>
</main>
</body>
</html>
Write Preview
Loading…
Cancel
Save