You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
50 lines
1.3 KiB
Markdown
50 lines
1.3 KiB
Markdown
# Worlding and Software
|
|
|
|
|
|
|
|
- I want to write about worlding around software
|
|
|
|
<br>
|
|
|
|
- How do you chose a particular programming language
|
|
- a coding style
|
|
- a development environment and ecosystem
|
|
- an infrastructure where to run the code
|
|
- and so on?
|
|
- These are **not just technical choices**
|
|
- but rather coding contingencies
|
|
|
|
<br>
|
|
|
|
- These contingencies are situated in precise contexts
|
|
- economical
|
|
- cultural
|
|
- creative
|
|
- political
|
|
- technical
|
|
- Programming then is not just sharing code, but sharing context.
|
|
- It's providing a perspective to look at the world
|
|
- before attempting to get some grip onto it with a script.
|
|
|
|
<br>
|
|
|
|
- How to provide a point of view through the lens of software?
|
|
- Who get to participate in this process of making meaning?
|
|
- How to create a discourse for the code to inhabit?
|
|
- How to stretch the affordances of code?
|
|
- besides
|
|
- technicality
|
|
- marketing
|
|
- advertisement
|
|
|
|
## Enter documentation
|
|
|
|
- Could software documentation
|
|
- _1_ be an ideal surface to build worlds
|
|
- _2_ be an interface between different knowledges
|
|
- _3_ be a device to trigger different kind of economy
|
|
- around situated software?
|
|
|
|
- How can situated practices inform the process of documenting software?
|
|
-
|