master
km0 2 years ago
parent 562cb97e74
commit e0cda17ed0

Binary file not shown.

After

Width:  |  Height:  |  Size: 68 KiB

Before

Width:  |  Height:  |  Size: 71 KiB

After

Width:  |  Height:  |  Size: 71 KiB

Before

Width:  |  Height:  |  Size: 120 KiB

After

Width:  |  Height:  |  Size: 120 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 68 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 63 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 63 KiB

Before

Width:  |  Height:  |  Size: 186 KiB

After

Width:  |  Height:  |  Size: 186 KiB

Before

Width:  |  Height:  |  Size: 122 KiB

After

Width:  |  Height:  |  Size: 122 KiB

Before

Width:  |  Height:  |  Size: 142 KiB

After

Width:  |  Height:  |  Size: 142 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 45 KiB

@ -20,9 +20,9 @@
- _situated software_
- software built around the needs of a community
- _example_ xpub has a small server
- server _=_ a machine connected to the www
- `server = a machine connected to internet`
- the soupboat
- _url_ hub.xpub.nl/soupboat
- _url_ `hub.xpub.nl/soupboat/`
- it is a shared space online
- where we can prototype websites, hosting applications, etc
- a place to call home in the internet
@ -41,6 +41,7 @@
<br>
- ![list](img/list.png)
- **a list**
- to explore the process of sharing knowledge and making worlds together around situated software
- the plan
@ -54,20 +55,43 @@
- _excercise_
- to articulate software documentation as a form of care
- a list
- that does not claim to catch everything
- where order matters
- but the relations between items matter more
- a space to define outlines
- sketch contours
- and them draw through
- without claim to catch everything
- where order
- matters
- but the relations between items
- matter more
- a space to sketch contours
- and then draw through
- a soft structure
- a way to preserve the reality of each item
- respect the origin of every source
- respect the heritage of each item
- without worries of tangling them together
- the idea for this pubblication is to experiment with the list
- experiment with the list
- as a writing machine
- that seems already fun
- here some prompts:
- **here some prompts:**
<br>
- ![dough](img/dough.png)
- **documentation as a form of care**
- _care for who?_
- the actors involved
- developer
- user
- mantainer
- the community
- everyone in the range of 1km from the source code
- aha it's a nice image
- because the source code is not just in 1 place
- but cloned in different machines
- _care for what?_
- infrastructure
- accessibility
- environment
- ethical values
- moral values
- what was the difference again?
- between infrastructure and ethical values
<br>
@ -82,13 +106,8 @@
- distance from the center is related to specificity
- more distant
- less technical
- similar to
- gravitational approach
- source code as a planet
- with satellites
- and orbits
- **documentation framework**
- _excercise_ try to map a documentation framework on the ꩜
- _excercise:_ try to map a documentation framework on the ꩜
- swirling from the outside
- _tutorials_
- learning oriented
@ -124,7 +143,32 @@
<br>
- ![LAMP](img/light.jpg)
- ![Moon](img/moon.png)
- software and gravity
- source code as a planet
- similar to the spiral
- gravitational approach
- satellites
- and orbits
- something about velocity
- speed of things related to code
- near the source code
- things change quickly
- far from source code
- documentation
- coding practices
- take more time to adjust
- code moves at the speed of light
- because it moves into fiber optic cables
- it ages fast
- its tempo flows at a total different pace
- compared to the pace of life
<br>
- ![Lamp](img/light.jpg)
- if software illuminates an unknown, it does so through an unknowable
- wendy hui kyong chun
- software is a lamp
- documentation is the light
- you can see the lamp if the light is lit
@ -133,40 +177,85 @@
- every lamp has its own light
- which
- kind of light
- lamp you bring for camping
- lamp you put near the bed
<br>
- **reference**
- Situated Software, Clay Shirky
- Situated Knowledges, Donna Harawai
- List and complexity: Annemarie Mol & John Law
- Diataxis Documentation Framework, Daniele Procida
- kind of lamp
- you bring for camping
- you put near the bed
- there is no such a thing as undocumented software
- because without documentation you cannot see it
- as a piece of code would print
- i am documented therefore i am
<br>
- ![tanuki](img/tanuki.jpg)
- the spirit animal of the developer is the tanuki
- like racoons they collect resources from the internet
- they patch together an answer from stack overflow and one from git
- they patch together snippets from
- stack overflow
- youtube comments of video tutorial
- git issues
- forum
- reddit
- code as an objet trouvé
- a dumpster diving approach to coding
- a matter of urgency
- a basic need
- seeing software happen
- holding code in your hands
- is more important
- than understanding it 100%
- there is always time
<br>
- ![river](img/river.jpg)
- how to navigate the river of softwaru
- how to structure the thesis writing machine ?
- Which level of granularity ?
- I would like to work with small text files
- but then the parsing could be trublesome ?
- small frontmatter files ?
- every entry of the list is a different file ?
- that is crazy, it would be much better to work with a DB
- but the db is obscure and requires CRUD
- that is not a problem...
- but i would prefer to have the files with the text thereeee
- writing the thesis in git
- git writing workflow
- wait also true that the thesis and the project are two different things
- but still
- everything is a file?
- the list and the river
- waters are shallow
- small text files are ok
- how to navigate a full thesis ?
- what about deep waters
- wait
- friendly reminder that
- thesis and the project are two different things
- _git_ writing workflow
- issues to annotate
<br>
- ![udon](img/udon.png)
- **about** this writing machine
- it is a _web-to-print_ app
- written in `Python`
- using `Flask`
- takes a plain text list
- written in `Markdown`
- and renders it in the browser
- as `HTML` document
- with some style and formatting
- so i can think through the form of the list
- while writing
- im using a _web-to-print_ approach
- because formatting with `CSS`
- is really handy
- sorcery
- the list can shuffle a lot
- without extra work
- find the machine on _git_
- _url_ `git.xpub.nl/kamo/writing-list`
<br>
- ![reference](img/reference.jpg)
- **references**
- Situated Software, Clay Shirky
- Situated Knowledges, Donna Harawai
- List and complexity: Annemarie Mol & John Law
- Diataxis Documentation Framework, Daniele Procida
- Images from
- Sumiyaki Monogatari, Takeno Shigeyasu
- (Tales of a Charcoal Burner)
- amazing manga
- 100% offtopic
- e va be
- when you like something
- you wanna share it

@ -11,7 +11,7 @@ def list():
return render_template('list.html', list = list)
@app.route('/img/<file>')
def send_file(file):
return send_from_directory(app.root_path + '/static/img/', file, conditional=True)
def send_img(file):
return send_from_directory(app.root_path + '/img/', file, conditional=True)
app.run(port="3000", debug=True)

@ -17,7 +17,7 @@ img {
}
li:first-child img {
height: 3rem;
height: 4rem;
vertical-align: bottom;
}
@ -41,7 +41,6 @@ li:last-of-type:after {
em {
display: inline-block;
/* background-color: rgb(224, 224, 224); */
font-weight: bold;
border: 2px solid currentColor;
@ -54,3 +53,7 @@ em {
font-size: 0.6rem;
line-height: 1rem;
}
code {
background-color: #eee;
}

Loading…
Cancel
Save