diff --git a/bibliography.md b/bibliography.md new file mode 100644 index 0000000..da5c40c --- /dev/null +++ b/bibliography.md @@ -0,0 +1,16 @@ +## Bibliography + +Ullman, E. (2017). _Life in code : a personal history of technology._ New York: Mcd, Farrar, Straus And Giroux. +Marino, M.C. (2020). _Critical code studies._ Editorial: Cambridge, Massachusetts: The Mit Press. + +TODO: + +add: + +- software studies lexicon +- aesthetic programming +- patterns of software + +how to cite?? + +- A Wishlist for Trans\*femminist Servers. 2022. https://etherpad.mur.at/p/tfs diff --git a/carpet/materials.md b/carpet/materials.md index f4ea801..47daa10 100644 --- a/carpet/materials.md +++ b/carpet/materials.md @@ -46,3 +46,7 @@ school operators of `+`, `-` , `x`, `/`? Importantly, Vee indicates that her aim is not to establish what coding literacy should look like; on the contrary, her premise is precisely that ‘prescriptions for literacy are always contingent’ (10) because literacies are always contingent. The framework of literacy helps her mobilize the extensive knowledge embedded in the study of literacy in order to provide a socially and historically informed perspective on coding as a literacy practice. Federica Frabetti. “Review of Annette Vee, Coding Literacy.” Computational Culture 8 (July 2021). http://computationalculture.net/review-of-annette-vee-coding-literacy/. + +## Parenting is programming, Ian Cheng + +Cheng: I wrote “parenting is programming” in the script without any cynicism. I actually believe that is true. Parents quite literally program children, and have an unavoidable influence on their entire life script, their anxiety or their comfort, their sense of trust and mistrust toward the world. But the critical thing most parents forget is that their role as parents, and the stuff they “programmed” into their kids, is scaffolding to get through the early years. But scaffolding is meant to fall away, and most parents don’t know when to let go of their kids, to stop parenting them, to let go of their role. And there isn’t much cultural guidance to help with modeling this type of letting go. In fact, many cultures still require an unhealthy attachment and debt to be constantly connected to one’s parents. I personally have anxiety about not being able to let go when my kids grow up, so I think about this a lot. I guess to answer your question, future education should include modeling how to exit; how to detach from one’s parents, one’s teachers, one’s coddling institutions, and go out and try things and fail and have adventures. Get some scars. Schools should have built-in “anti-school” prep, as counterproductive as that might sound to the big business of schools. diff --git a/chapters/00_intro.md b/chapters/00_intro.md index 9e8481f..eb8686f 100644 --- a/chapters/00_intro.md +++ b/chapters/00_intro.md @@ -1,30 +1,19 @@ -## 0. Worlding and software _(2000)_ - 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. -Preparing for a job interview, trending technologies, curiosity and boredom, to name a few. A talk that touches on esolangs as form of frugality, a collegue passionate about live coding that drags you to an algorave night, a crypto-boyfriend, the tech stack of a company, a drastic turn of events, etc. etc. +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. These contingencies are situated in specific contexts. -Programming then is not just sharing code, but sharing context. A significant statement about our relationship to the world, and how we organize our understanding of it (Ullman, 2017). A point of view and a perspective to look at reality, before attempting to get some grip onto it with a script. A way to deal with both the software and hardware circumstances of code (Marino, 2020), but also create community and relations with _non-code entities_ (Mackenzie, 2006). +Programming then is not just sharing code, but sharing context. A significant statement about our relationship to the world, and how we organize our understanding of it (Ullman, 2017). A point of view and a perspective to look at reality, before attempting to get some grip onto it with a script. A way to deal with both the software and hardware circumstances of code (Marino, 2020), but also engaging with the sociality and communities around it. 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? For what cause? 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? - -### 1.3 Propose documentation as a surface to address these issues - -1. Welcoming diverse knowledges -2. Lowering barriers and create entry points -3. Orientate software in the world - -- _(500)_ +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? -## References +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. -Ullman, E. (2017). _Life in code : a personal history of technology._ New York: Mcd, Farrar, Straus And Giroux. -Marino, M.C. (2020). _Critical code studies._ Editorial: Cambridge, Massachusetts: The Mit Press. +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. -https://vimeo.com/105069079 +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. -Tsutomu Nihei, Paul, S., Montclare, B. and Macasocol, J. (2005). _Blame! Volume 1_. Los Angeles, Ca: Tokyopop. +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) diff --git a/chapters/01_interface.md b/chapters/01_interface.md new file mode 100644 index 0000000..f69b71d --- /dev/null +++ b/chapters/01_interface.md @@ -0,0 +1,5 @@ +_can documentation be an interface between different knowledges?_ + +- interface between code, developer, world +- post meritocracy manifesto +- trans\*femminist server whishlist diff --git a/chapters/02_economy.md b/chapters/02_economy.md new file mode 100644 index 0000000..4701ed3 --- /dev/null +++ b/chapters/02_economy.md @@ -0,0 +1,3 @@ +_can documentation trigger different kinds of economy around software?_ + +- 360 degrees of proximity diff --git a/chapters/03_world.md b/chapters/03_world.md new file mode 100644 index 0000000..d5114f5 --- /dev/null +++ b/chapters/03_world.md @@ -0,0 +1,4 @@ +_be an ideal surface to build worlds?_ + +- the screenless office +- ian cheng diff --git a/notes.md b/notes.md index b1aa06e..97e47a5 100644 --- a/notes.md +++ b/notes.md @@ -1,5 +1,23 @@ -# 12/01/2023 +- be a mean to explore these contingencies? -- Table of contents (Structure + Math) -- Condensed simulation -- + - coding contingencies + - software studies + - documentation to address issues + 1. Welcoming diverse knowledges + 2. Lowering barriers and create entry points + 3. Orientate software in the world + - **practical example!!!** + +- be an interface between different knowledges? + + - interface between code, developer, world + - post meritocracy manifesto + - trans\*femminist server whishlist + +- be an ideal surface to build worlds? + + - the screenless office + - ian cheng + +- be a device to trigger different kinds of economy around situated software? + - 360 degrees of proximity