From e2c1c29b6b8dcb8965e5a7612a76fd00b0168f9f Mon Sep 17 00:00:00 2001 From: "kam (from the studio)" Date: Tue, 31 Jan 2023 13:59:25 +0100 Subject: [PATCH] organize stuff --- .../cod_cot.md | 35 ------------------- carpet/{old_coding_cont.md => simulation.md} | 0 chapters/00_intro.md | 30 ++++++++++++++++ 3 files changed, 30 insertions(+), 35 deletions(-) rename chapters/00_coding_contingencies.md => carpet/cod_cot.md (68%) rename carpet/{old_coding_cont.md => simulation.md} (100%) create mode 100644 chapters/00_intro.md diff --git a/chapters/00_coding_contingencies.md b/carpet/cod_cot.md similarity index 68% rename from chapters/00_coding_contingencies.md rename to carpet/cod_cot.md index c32dc07..099d1ad 100644 --- a/chapters/00_coding_contingencies.md +++ b/carpet/cod_cot.md @@ -1,21 +1,3 @@ -## 1. Coding Contingencies _(2000)_ - -Situate software as cultural object and propose documentation as a surface to explore it. - -### 1.1 Context around software, besides technicality - -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. - -Personal decisions, 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. - -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 space and relations with _non-code entities_ (Mackenzie, 2006). - -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? - There is a difference in scale of space and time between our biological and social selves, and the internal clock of a computer, or the reach of its network. This often leads us to picture wrong images of the technological complexity we are participating in. That's why in order to debug complexity we probably first need to debug software (Shirky, 2014). Understand how does it work, or why it doesn't work the way we expect, either in its technical, cultural, or environmental outcomes. Unpack what can be changed and adjusted, and being able to reason about it. @@ -71,20 +53,3 @@ b. --- Without guidance seems impossible to orientate in this maze. - -### 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)_ - -## References - -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. - -https://vimeo.com/105069079 - -Tsutomu Nihei, Paul, S., Montclare, B. and Macasocol, J. (2005). _Blame! Volume 1_. Los Angeles, Ca: Tokyopop. diff --git a/carpet/old_coding_cont.md b/carpet/simulation.md similarity index 100% rename from carpet/old_coding_cont.md rename to carpet/simulation.md diff --git a/chapters/00_intro.md b/chapters/00_intro.md new file mode 100644 index 0000000..9e8481f --- /dev/null +++ b/chapters/00_intro.md @@ -0,0 +1,30 @@ +## 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. + +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). + +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)_ + +## References + +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. + +https://vimeo.com/105069079 + +Tsutomu Nihei, Paul, S., Montclare, B. and Macasocol, J. (2005). _Blame! Volume 1_. Los Angeles, Ca: Tokyopop.