@ -161,7 +161,7 @@ And then a list of possible references
<!--- Mackenzie, A (2006) Cutting Code; Software and Sociality, International Academic Publisher -->
<!--- Suchman, L A (1987) Plans and Situated Actions: The Problem of Human-Machine Communication, Cambridge University Press -->
<!-- Balibar, É (2020) On Universals: Constructing and Deconstructing Community, Fordham University Press -->
- Cantwell Smith, B (1996) On the Origin of Objects, Bradfor Book
<!--- Cantwell Smith, B (1996) On the Origin of Objects, Bradfor Book-->
<!--- Knuth, D E (1973) The Art of Computer Programming, Addison-Wesley -->
@ -170,6 +170,7 @@ And then a list of possible references
- Brodie, L (1984) Thinking Forth, Punchy Publising
- Wendy Hui Kyong Chun, "On Software, or the Persistence of Visual Knowledge" (2005) Grey Room. 18
- Lethbridge, Chantelle & Sim, Susan & Singer, Janice. (1999). Software Anthropology: Performing Field Studies in Software Companies.
- Crowston, Kevin and Howison, James, "The Social Structure of Open Source Software Development Teams" (2003). School of Information Studies - Faculty Scholarship. 123.
@ -149,9 +149,9 @@ Once you identify these you can begin a chapter outline. -->
I want to write about worlding 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.
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.
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.
These contingencies are situated in precise contexts. Programming then is not just sharing code, but sharing context. It's providing a point of view and a perspective to look at the world, before attempting to get some grip onto it with a script.
More specifically, I would like to focus on software documentation as a surface for world-building.
@ -163,13 +163,13 @@ Since last year I'm prototyping writing machines in order to keep track of what
The topological way to think and write the thesis is to be find somewhere around:
The topological way to think and write the thesis is to be found somewhere around:
- the list form used by LW in the Tractatus,
- the branching and merging pathways of version control systems, and
- the content aggregation approach of bookmarking tools such as are.na
At the moment I can see it as a feed with a tagging system. The plan is to gather contents and curate them in a non-linear fashion, so instead of following the index as a series of step, imagine to read it as a coral-like creature, with materials forking and interfering with each other.
At the moment I can see it as a feed with a tagging system. The plan is to gather contents and curate them in a non-linear fashion, so instead of following the index as a series of steps, imagine to read it as a coral-like creature, with materials forking and interfering with each other.
These contents will be a mix of diverse registry, from the essayistic to the technical to the anedoctic, in order to have several layers of accessibility. The consistency of the discourse will vary: some parts will be more narrative and some other more scattered.
