hierarchies

main
km0 2 years ago
parent 4b4741c7bf
commit 80e72b727e

@ -1,6 +1,6 @@
# Who is reading ## Who is reading
``` `
documentation as a publishing surface? documentation as a publishing surface?
yes because yes because
@ -10,9 +10,9 @@ yes because
yes but yes but
it should be less hostile - see welcoming writing it should be less hostile - see welcoming writing
it should stop assuming reader - see natural readers it should stop assuming reader - see natural readers
``` `
## Getting started ### Getting started
`("Getting startled" could also make for a nice title)` `("Getting startled" could also make for a nice title)`
Reading undocumented code feels like being an ant walking on a big painting. You can see the strokes of a brush and have an intuition of their direction, but what's missing is an overall idea of how the composition flows. Documentation provides guidance through the bunch of functions and statements that makes software, a bird's eye perspective. It is often the first thing one gets across when approaching a new library or programming language, and it shapes the way a developer thinks about particular piece of code. Reading undocumented code feels like being an ant walking on a big painting. You can see the strokes of a brush and have an intuition of their direction, but what's missing is an overall idea of how the composition flows. Documentation provides guidance through the bunch of functions and statements that makes software, a bird's eye perspective. It is often the first thing one gets across when approaching a new library or programming language, and it shapes the way a developer thinks about particular piece of code.

@ -12,13 +12,13 @@ A part of theoretical examples of technology and worlding: Trans\*feminist Serve
A part of case studies. The soupboat. Avantwhatever.net. Queer Motto API. The Screenless Office. The uxn ecosystem. `list wip` A part of case studies. The soupboat. Avantwhatever.net. Queer Motto API. The Screenless Office. The uxn ecosystem. `list wip`
## Going with the flows ### Going with the flows
There could be several approaches for making worlds around software. Here are some keywords that refer to the kind of flow these worlding techniques activate.Drafted here are three directions: to _reclaim_ is to get something back: something that was stolen, or taken away, or lost, or forgotten. To _reenchant_ means to intercept and reorientate towards different directions. To readjust a process, or to move for a different purpose. To _reassure_ serves as prompt to keep going. It helps making meaning together, and refresh ideas. It offers way to register choices, keep track and share what has been done so far. There could be several approaches for making worlds around software. Here are some keywords that refer to the kind of flow these worlding techniques activate.Drafted here are three directions: to _reclaim_ is to get something back: something that was stolen, or taken away, or lost, or forgotten. To _reenchant_ means to intercept and reorientate towards different directions. To readjust a process, or to move for a different purpose. To _reassure_ serves as prompt to keep going. It helps making meaning together, and refresh ideas. It offers way to register choices, keep track and share what has been done so far.
These labels are open and loose, overlapping and not mutually exclusive, temporary and on the move. They are meant to change, to expire fast, and going bad even faster: they require continuous treatments and repeated efforts. That's why I'm naming them all after the _re_ prefix: to aknowledge their being in progress, second hand again, already contaminated. Borrowed by friends and foes, that had borrowed themselves from someone else. One should diffidate of these categories because they're instable. Nonetheless, they offer ways to visualize different strategies to create worlds around software. These labels are open and loose, overlapping and not mutually exclusive, temporary and on the move. They are meant to change, to expire fast, and going bad even faster: they require continuous treatments and repeated efforts. That's why I'm naming them all after the _re_ prefix: to aknowledge their being in progress, second hand again, already contaminated. Borrowed by friends and foes, that had borrowed themselves from someone else. One should diffidate of these categories because they're instable. Nonetheless, they offer ways to visualize different strategies to create worlds around software.
``` `
reclaim take back reclaim take back
reenchant intercept reenchant intercept
reassure keep going reassure keep going
@ -26,9 +26,9 @@ reassure keep going
reclaim renegotiate, recuperate, remember, refuse, reactivate reclaim renegotiate, recuperate, remember, refuse, reactivate
reenchant redirect, rebirth, reboot, rebrand, redeem reenchant redirect, rebirth, reboot, rebrand, redeem
reassure refrain, refresh, regret, reaffirm, register, readme reassure refrain, refresh, regret, reaffirm, register, readme
``` `
## reclaim ### reclaim
There seems to be a risk in reducing sociality around software to a conflict between "friends and foes": a risk to reproduce forms of exclusion and violence typical of the IT world. To just swap good and bad, and offer clean solutions. Try instead to apply Chantal Mouffle's concept of agonistic politics to software development intended as struggle between different hegemonic projects. There seems to be a risk in reducing sociality around software to a conflict between "friends and foes": a risk to reproduce forms of exclusion and violence typical of the IT world. To just swap good and bad, and offer clean solutions. Try instead to apply Chantal Mouffle's concept of agonistic politics to software development intended as struggle between different hegemonic projects.
@ -40,7 +40,7 @@ Think about projects related to accessibility, and space built by and for people
Think about the efforts to create safe spaces to learn. Think about the efforts to create safe spaces to learn.
## reenchant ### reenchant
Reenchanting code cannot be just a process of rebranding. Cannot be just a matter of changing the visual identity of the documentation, or washing it green or pink or black, or to capitalize on the inclusion of minorities. Reenchanting code cannot be just a process of rebranding. Cannot be just a matter of changing the visual identity of the documentation, or washing it green or pink or black, or to capitalize on the inclusion of minorities.
@ -79,4 +79,4 @@ Staying low
## reassure ### reassure

Loading…
Cancel
Save