From 6fab7b67861a5e5a3d99b8a5bbe29ccf70ab7465 Mon Sep 17 00:00:00 2001 From: km0 Date: Sun, 26 Mar 2023 16:51:33 +0200 Subject: [PATCH] backdoor structure --- chapters/01_entry_points.md | 12 ++++++---- chapters/02_backdoors.md | 47 ++++++++++++++++++++++++++++++++++++- 2 files changed, 53 insertions(+), 6 deletions(-) diff --git a/chapters/01_entry_points.md b/chapters/01_entry_points.md index 80b04af..fcab43c 100644 --- a/chapters/01_entry_points.md +++ b/chapters/01_entry_points.md @@ -118,7 +118,9 @@ problems of contents: too much technical knowledge is required to read the documentation itself. the docs results impossible to read, and there is no knowledge one can make out of it if not already educated. not filtering knowledge becomes a filter to who can access it. -programming means building abstractions on top of abstractions, ad libitum. two different approaches here on how to deal with this intimidating stack of complexity. +programming means building abstractions on top of abstractions, ad libitum. + +two different approaches here on how to deal with this intimidating stack of complexity. one is sequential, from the ground up. see nand to tetris. from logic gates to a programmable comptuer. it gives insights on how a machine works starting from scratch. @@ -134,7 +136,7 @@ bottom-up / top-down a different kind of approach is more modelled on the way technology and coding confront us in real life. one often starts from the middle. -programming for advanced beginners series. decoupled tutorial: no specific language, but rather specific case studies to understand practically and first hand. here the series present a practical problem, such as how to code an _hygienic login system_. here like in nand to tetris things are built gradually. here however the process is iterative and circular, instead of linear. implementations are put in place provisionally and then reiterated and developed more, introducing new concepts not as hardcoded procedures but as a result of emerging problems. +programming for advanced beginners series. decoupled tutorial: no specific language, but rather specific case studies to understand practically and first hand. here the series present a practical problem, such as how to code an _login system_. like in nand to tetris things are built gradually. here however the process is iterative and circular, instead of linear. implementations are put in place provisionally and then reiterated and developed more, introducing new concepts not as hardcoded procedures but as a result of emerging problems. the entry points here are multiple as the spokes in a bicycle wheel, as they come from different directions and don't frame the code as a prescriptive and rigid system, but rather as a crafted balance between different forces in play @@ -149,7 +151,7 @@ sometimes code is about performance, sometimes is about flexibility, sometimes i not only technical problems, but also how they are formulated -usage of language in technical documentation refer to a particular context +usage of language in technical documentation refer to a particular context and public mainly address male reader and gendered roles @@ -195,7 +197,7 @@ documentation that does not reflect the behaviours of the code is a curse that u - Updates, corrections, additions, translations -there are a moltitude of ways in which a change in the codebase reflects in the documentation. New feature asks for new sections. updates and breaking changes to with the previous versions require instructions on how to migrate to the new one. +there are a moltitude of ways in which a change in the codebase reflects in the documentation. New feature asks for new sections. updates and breaking changes to with the previous versions require warnnings and instructions on how to migrate to the new one. bugs and unexpected behaviours of the code are to be pointed out. deprecated functions need to be trimmed. on top of that all the editorial effort has to be considered. corrections and line editing. internationalization and localization. @@ -211,6 +213,6 @@ documentation as gendered labour, and subaltern labour. examples: excerpt from p - Post-meritocracy manifesto -all these effort are a confirm of what proposed by the post meritocracy manifesto: the making of software is not just programming. the makers of software are not just engineers. +all these effort are a confirmation of what proposed by the post meritocracy manifesto: the making of software is not just programming. the makers of software are not just engineers. code documentation is a surface where all the sociality, context, and relations around software are visible. a surface that in turn can be activated to reach the different kinds of actors that surround it. kinda like a backdoor diff --git a/chapters/02_backdoors.md b/chapters/02_backdoors.md index d517b9d..501cd2f 100644 --- a/chapters/02_backdoors.md +++ b/chapters/02_backdoors.md @@ -1,5 +1,48 @@ ## 2. Documentation as a backdoor + +- when the entry points are blocked one has to search for backdoors + +- little context for backdoors + +- not only to participate in the making of software + +- but also to inject values, + +- to expose people usually out of reach to different contexts + +- by transforming coding contingencies? to create context that inform technical choices + + +from reaching a public to creating a public + +- examples + +1. politics of participation and representation + +- from the trans\*feminists servers manifesto to the queer motto api to the 360 degrees of proximity + +- from the discussion about accessibility in p5js to alt-text as poetry + +- create new spaces for participation, validate participation + + +2. aesthetic practices - hello worlding + +- uxn ecosystem: re reading esolangs, plan-9, and virtual machines through the ecological lens + +- the screenless office read through tiger dingsun's chimeric worlding + +- aesthetic programming as a bridge between software studies and creative coding + + +[ fade out towards outro ] + + + + + + ```note it could be nice to have a small glossary / way to situate / elaborate on these terms: (or even better to use them to organize the chapter and the examples) @@ -30,7 +73,9 @@ Possible structure for this chapter: - aesthetic programming - p5.js on accessibility features - - trans*femminist servers and 360 degres of proximity + + - trans*femminist servers + - 360 degres of proximity - queer motto api