- groud with a concrete example to make the intro more accessible
- adjust contingencies paragraph to better address intended audience
---
How do you choose a particular programming language, a coding paradigm, a development environment, an infrastructure where to run the code, and so on? These are not just technical choices, but rather coding contingencies.
The IT class program of a public school, the job requirements for working in a tech company. An Arduino board received as gift from your daughter. A collegue passionate about experimental music that drags you to a live coding concert. The storming of NFTs & flooding of consumer-ready AI services in popular culture.
@ -8,12 +15,12 @@ Programming then is not just sharing code, but sharing context. A significant st
It's an approach that helps us to think about software as a cultural object. Something "deeply woven into contemporary life –economically, culturally, creatively, politically– in manners both obvious and nearly invisible." (Software Studies, 2009), and not just as technical tool existing in a vacuum.
An object that, in turn, can be used to probe its surroundings. Who is developing? Who is paying and why? Who is gonna use it? How is it structured? It is a big and centralized system or a loose collection of small and interchangable tools? How long is it supposed to last? How can be fixed if it breaks?
An object that, in turn, can be used to probe its surroundings. Who is developing? Who is gonna use it? Who is paying and why? How is it structured? It is a big and centralized system or a loose collection of small and interchangable tools? How long is it supposed to last? How can be fixed if it breaks?
The main focus of this research is to propose and explore software documentation as a surface where these questions can be addressed. Where the complexity of code doesn't act as a black box, and ideas and choises behind development are really open source.
The main focus of this research is to propose and explore software documentation as a surface where this kind of questions can be addressed. Where the complexity of code doesn't act as a black box, and ideas and choises behind development are really open source.
Working at the intersection between people, code and computer, documentation seems a good place where to aknowledge the different voices involved in the making of software. A way to question hostile and gendered IT environments, creating welcoming spaces for diverse identities, lowering barriers, and offering multiple entry points.
There is a massive labor of care besides technicalities, labor that is often marginalized by tech culture. No one wants to write documentation, nor wants to pay someone to do it (Gabriel, 1996), plus is a difficult and delicate practice, and the result is lack of docs. At the same time, this very scarcity could be used as a starting point.
There is a massive labor of care besides technicalities, labor that is often marginalized by tech culture. No one wants to write documentation, nor wants to pay someone to do it (Gabriel, 1996), plus is a difficult and delicate practice. The result is lack of documentation. At the same time, this very scarcity could be used as a starting point.
Documentation could be a space for the political in the software. A surface that could host principles in close contact with code, letting them entangle and shape each other. A way to orientate our instruments towards non-extractive relationships, but in the meantime, being accountable for the ones they are complicit with. (A Wishlist for Trans\*feminist Servers, 2022)
Documentation could be a space to reclaim given margins. A surface that could host principles in close contact with code, letting them entangle and shape each other. A way to orientate our instruments towards "non-extractive relationships, but in the meantime, being accountable for the ones they are complicit with." (A Wishlist for Trans\*feminist Servers, 2022)
