@ -134,12 +134,12 @@ Developing togheter with others it's a way to renegotiate priorities when develo
---
As a piece of code would write: I am documented, therefore I am.
And viceversa. Undocumented software is invisible, but for the eyes of their own developers. And eventually, it begins to fade as soon as the developer looks away.
---
As a piece of code would write: I am documented, therefore I am.
## Coding Contingencies
Coding is not just production of software, but also production of knowledge. A dialogue between human and more-than-human actors. The guestlist of this conference of the bits is often compiled by chance: the choice of a particular programming language, the coding style, the development environment and ecosystem, the infrastructure that runs the code, and so on, are the result of specific contingencies.
What mode of address do you want to assume? How do you want your text to speak to the reader?
(this dictates the form: essayistic, academic, narrative, non-linier, script; diary; field report)
Be clear about HOW you want to tell your story.
Key issues you want to explore (what research questions do these lead to?)
Please think of only 3 key issues.
Once you identify these you can begin a chapter outline. -->
## Coding Contingencies.
I want to write about worldbuilding around software.
How do you chose a particular programming language, the coding style, the development environment and ecosystem, the infrastructure which runs the code, and so on?
These are not just technical choices, but rather coding contingencies.
These contingencies are situated in precise contexts. Programming then is not just sharing code, but sharing context. It's to provide a point of view and a perspective to look at the world, before attempting to get some grip onto it with a script.
To make place for the code turns to be a necessary act of care in the process of sharing knowledge. Software documentation as an act of worldbuilding.
