intro for chap 3

chapters/03_hello_worlding.md

@@ -4,11 +4,39 @@ The third section is focused on worlding, and the relation between code, documen
 
 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)
 
-
 _References for technology and worlding_: Trans\*feminist Servers, Zach Blas, Tiger Ding Sun, James Bridle, Soon and Cox, Richard Gabriel.
 
 _Case studies_: The soupboat. Avantwhatever.net. Queer Motto API. The Screenless Office. The uxn ecosystem. `list wip`
 
+
+### Documentation as backdoor
+
+```note
+(not really sure where to put this)
+(need more glue here and there between these paragraphs)
+- pure programming: running away from the political
+- literacy and exposition to certain concepts
+- weaving technical and political together
+```
+
+Programming, as most of all the other technical worlds out there, strive to be purely technical. Immaculate from the sin of politics. It happens to read comments from users that demand to keep politics out from code repository. Building on the western tradition of separate fields of study, coding wants just to be coding. Everything is about performance and speed, new updates and features. A space where all problems are mechanical and can be solved.
+
+But it wouldn't be fair to think that programmers simply don't care. Sometimes it's just a matter of being exposed to certain ways of thinking. Before the bachelor at the Accademy of Fine Arts for example, I've never been exposed to the writings of Donna Haraway, and I had no idea that concepts from feminism could have been so relevant for me.
+
+```note
+if you cite Haraway better explain why it's important for you etc
+```
+
+Ellen Ullman is a programmer and writer, one of the few women working as developer in the Silicon Valley during the 80s and 90s. The combination of coming from the humanities, being a self-taught programmer, and especially being a woman made her the archetypical outsider in the IT industry. At the same time, this very position granted her a unique ethnographic perspective, capable of looking critically at this environment, both from the inside and from the outside. In more than one passage for example, she laments the general lack of literacy between many of her coworkers.
+
+Here code documentation could work as a backdoor: hacking its way to people that have never been exposed to certain topics. A way to offer an entry points to other worlds, and ground political choices into technical details.
+
+_Aesthetic Programming - A Handbook of Software Studies_, by Winnie Soon and Geoff Cox is an example on how to weave together these different discourses. The book explains the basic concepts of programming: it starts from variables and loops, arriving to more complex topics such as machine learning or speech recognition. The technical curriculum offered is in line with other similar resources that target non-engineers. What's different here is a commitment to critically enquiry themes such as colonialism, racism, gender and sexuality, capitalism and class, and how are they embedded in code.
+
+Soon and Cox prepared these lessons for students enrolled in a design institution, and curated the pubblication targetting a public somehow familiar with the discourses around software studies. Thanks to the vantage point of writing documentation for beginners, they could be super explicit and go all out with generous amount of references.
+
+Note that this work of care is not always possible. Sometimes the context doesn't feel safe to be so exposed, or there are no energies, or time, or means available. Sometimes it is necessary to act in a more nuanced way. To leave breadcrumbs and sow seeds. Or to raise voice and be firm. Different ways for different moments.
+
 ### Going with the flows
 
 There could be several approaches for making worlds around software. Here are some keywords to refer to the kind of flow these worlding practices activate. To _reclaim_ is to get something back: something that was stolen, or taken away, or lost, or forgotten. To _reenchant_ means to intercept and reorientate towards different directions. To readjust a process, or to move for a different purpose. To _reassure_ serves as prompt to keep going. It helps making meaning together, and refresh ideas. It offers way to register choices, keep track and share what has been done so far.
@@ -91,12 +119,20 @@ The same with DuskOS, a small operative system that reactivate the ancient progr
 
 ### Reassure
 
-We tend to put ourselves in difficult situations. By aknowledging complex problems, we aknowledge also the impossibility for simple solutions.
 
-It would be easier to believe in technosolutionism: to think that issues such as biased algorithms or discrimination in IT could simply be solved by installing a new product, or updating our software to the last version, or writing code documentation following a new innovative framework.
 
 
 
+
+
+
+
+
+
+We tend to put ourselves in difficult situations. By aknowledging complex problems, we aknowledge also the impossibility for simple solutions.
+
+It would be easier to believe in technosolutionism: to think that issues such as biased algorithms or discrimination in IT could simply be solved by installing a new product, or updating our software to the last version, or writing code documentation following a new innovative framework.
+
 But then what are we doing? If all these efforts to write documentation are not revolutionary, if they don't bear solutions, it they tackle minimal portions of major and systemic issues. Where is the twist in this idea of code documentation as publishing practice?
 
 Three sources that could be explored here relate to an alternative to the model of technosolutionism

notes.md

@@ -4,18 +4,8 @@
 ## Bouldering and secrecy
 
 - suckless and bouldering: different levels of documentation
-
 - documentation as backdoor
-
+--> but for a different target
-Programming, as most of all the other technical worlds out there, strive to be purely technical. Immaculate from the sin of politics. It happens to read users that demand to keep politics out from code repository, even in FLOSS projects that are inherently political.  Building on western tradition of separate fields of study, coding wants to be just coding. The topics around software all concern performance and speed, new updates and features. A space where all problems are technical and can be solved.
-
-Don't think that programmers don't care. Sometimes it's just a matter of being exposed to certain ways of thinking. Before the bachelor at the Accademy of Fine Arts I've never been exposed to the writings of Donna Haraway for example, and I had no idea that feminism could have been something also for me to participate.
-
-Here code documentation could work as a backdoor: hacking its way to people that have never been exposed to certain topics. A way to offer an entry points to other worlds, and ground political choices into technical details.
-
-_Aesthetic Programming - A Handbook of Software Studies_, by Winnie Soon and Geoff Cox is a perfect example. The book explains the basic concepts of programming for: it starts from variables and loops to arrive to more complex topics such as machine learning. The technical offering of the text is in line with other similar resources that serves as introduction to programming for non-engineers. What's different here is a continuous commitment to critically enquiry themes such as colonialism, racism, gender and sexuality, capitalism and class, and how are they embedded in code.
-
-
 
 - stealth