diff --git a/img/spoonbils.jpg b/img/spoonbils.jpg new file mode 100644 index 0000000..091fc6f Binary files /dev/null and b/img/spoonbils.jpg differ diff --git a/readme.md b/readme.md index 3f253fe..eeabda9 100644 --- a/readme.md +++ b/readme.md @@ -51,21 +51,26 @@ The critical and theoretical research will be weaved around the actual documenta Strategies to share workloads and collaboration Strategies to take care of shared piece of software. --> -## 1. Coding Contingencies - -_(2000)_ +## 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 -_(500)_ +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 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 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. -Refer to software studies +- References to software studies +- _(500)_ ### 1.2 Introduce issues around software -_(1000)_ +![three spoonbills](img/spoonbils.jpg) Outline a map of critical issues related to software culture, grouping them in three main flavours: @@ -76,17 +81,17 @@ Outline a map of critical issues related to software culture, grouping them in t 3. **The universal solution™** - Techno solutionism, gray tech, ideology -### 1.3 Propose documentation as a surface to address these issues +- _(1000)_ -_(500)_ +### 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 -## 2. Documentation as an interface +- _(500)_ -_(3000)_ +## 2. Documentation as an interface _(3000)_ Aknowledge documentation as crossroad for different actors, as intersection between code, machines, developers, users. Articulate it as a vantage point from where to reason about software. @@ -101,28 +106,34 @@ _What is written?_ - rather to a form of care (for users, for software, for context) - in the context of situated software +- _(750)_ + ### 2.1 Welcoming diverse knowledges _Who is writing?_ - - How does development and technical writing interact? - - Is the technical writer a subaltern position in the industry of software development? - - Who gets to write, and who is forced to? - - No one wants to write documentation, or pay someone to do it - - Documentation as a form of care +- How does development and technical writing interact? +- Is the technical writer a subaltern position in the industry of software development? +- Who gets to write, and who is forced to? +- No one wants to write documentation, or pay someone to do it +- Documentation as a form of care _Who will read?_ _Who is addressed?_ - - Assuming a certain kind of reader (often male, often white, often with formal education) - - _Read the feminist manual_ (Karayanni, 2021) - - _Programming for the millions_ (Ullman, 2016) +- Assuming a certain kind of reader (often male, often white, often with formal education) +- _Read the feminist manual_ (Karayanni, 2021) +- _Programming for the millions_ (Ullman, 2016) + +- _(750)_ ### 2.2 Lowering barriers and create entry points - - _Who can access?_ - - [welcome.js](https://jamesbridle.com/works/welcome-js) (Bridle, 2016) - - _Debugging_ (P5js Education Working Group, 2015) +- _Who can access?_ +- [welcome.js](https://jamesbridle.com/works/welcome-js) (Bridle, 2016) +- _Debugging_ (P5js Education Working Group, 2015) + +- _(750)_ ### 2.3 Orientate software in the world @@ -139,24 +150,32 @@ _How are we making it?_ - _Wheatering software winter_ (100R, 2022) - Ways of Being (Bridle, 2022) +- _(750)_ + ## 3. Situated software requires situated documentation (3000) ### 3.1 Situated software lifecycle. Inner public, outer public. - - Inner public is the target audience of a situated software. The community where it has been developed. _Private public._ - - Outer public is others: different communities that approach to it later on or for different purposes. _Public public._ - - What role plays documentation in these two moments? +- Inner public is the target audience of a situated software. The community where it has been developed. _Private public._ +- Outer public is others: different communities that approach to it later on or for different purposes. _Public public._ +- What role plays documentation in these two moments? + +- _(1000)_ ### 3.2 A recipe in the making. Documenting situated practices as an ongoing process. - - Techno-solutionism reversed: are we the solution to our tools' problems? - - A praise for partial solutions +- Techno-solutionism reversed: are we the solution to our tools' problems? +- A praise for partial solutions + +- _(1000)_ ### 3.3 Code as common. Documentation as loose interface between different needs. - - Situated documentation is tailored on specific needs, and produced from specific perspectives. - - How can it resonate with different ones? +- Situated documentation is tailored on specific needs, and produced from specific perspectives. +- How can it resonate with different ones? + +- _(1000)_