From a2de349b091758c5b29094c796b576e201834b47 Mon Sep 17 00:00:00 2001 From: km0 Date: Wed, 5 Apr 2023 18:37:54 +0200 Subject: [PATCH] intro structure --- chapters/00_intro.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/chapters/00_intro.md b/chapters/00_intro.md index 0f96b3a..596526e 100644 --- a/chapters/00_intro.md +++ b/chapters/00_intro.md @@ -28,10 +28,6 @@ By stripping down every trace of professionalism and formal education, let's agr This thesis explores code documentation as an interface. A permeable passage from context to code, and from code to context. -```note -ùpdate once again the next paragraphs -``` - -The first part focuses on who is reading, who is addressed, and who is left out. Code documentation brings an understanding on software by disclosing its magic. It reveals what can be done with it, and where are the limits. By lowering barriers and creating entry points, documentation broadens participation. By reaching not just beginners, but experienced programmers as well, it affects thinking about software continuously, and from different perspectives. In order to create accessible entry points and speak to different people however, it's necessary to question the usage of language, to criticize the amount of energies required for writing, and to address problems of inclusivity within tech communities. +The first part focuses on languages, formats and approaches of code documentation, to broaden participation in the making of software by questioning who is reading, who is addressed, and who is left out. Code documentation brings an understanding on software by disclosing its magic. It reveals what can be done with it, and where are the limits. By lowering barriers and creating entry points, documentation broadens participation. By reaching not just beginners, but experienced programmers as well, it affects thinking about software continuously, and from different perspectives. In order to create accessible entry points and speak to different people however, it's necessary to question the usage of language, to criticize the amount of energies required for writing, and to address problems of inclusivity within tech communities. The second section is focused on worlding, and the relation between code, documentation practices and political aesthetic. Here documentation is seen as a surface that could host principles in close contact with algorithms, 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) A backdoor to inject context around technical and non-technical choices.