rq and br

txt/brainstorm.md

@@ -101,7 +101,7 @@
 -   A federated code of conduct?
 -   An entangled soup of documentation resources?
 -   I don't know yet
--   But what i can imagine is a process:
+-   But i can imagine a process:
 
 <br>
 
@@ -125,3 +125,5 @@
 -   (varia)
 -   _3_
 -   let's see
+
+<br>

txt/rq.md

@@ -0,0 +1,44 @@
+-   **worlding and software**
+
+-   I want to write about worlding around software
+
+<br>
+
+-   How do you chose a particular programming language
+-   a coding style
+-   a development environment and ecosystem
+-   an infrastructure where to run the code
+-   and so on?
+-   These are **not just technical choices**
+-   but rather coding contingencies
+
+<br>
+
+-   These contingencies are situated in precise contexts
+-   economical
+-   cultural
+-   creative
+-   political
+-   Programming then is not just sharing code, but sharing context.
+-   It's providing a perspective to look at the world
+-   before attempting to get some grip onto it with a script.
+
+<br>
+
+-   How to provide a point of view through the lens of software?
+-   Who get to participate in this process of making meaning?
+-   How to create a discourse for the code to inhabit?
+-   How to stretch the affordances of code?
+-   besides
+-   technicality
+-   marketing
+-   advertisement
+
+<br>
+
+-   How can situated practices inform the process of documenting software?
+-   Could software documentation
+-   _1_ be an ideal surface to build worlds
+-   _2_ be an interface between different knowledges
+-   _3_ be a device to trigger different kind of economy
+-   around situated software?