kamo
/
thesis
1
2
Fork 0
Code Issues Pull Requests Releases Wiki Activity
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.
main
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '86a65f69a4'
${ noResults }
thesis/readme.md

1.2 KiB
Raw Blame History

Worlding and Software

3D cover

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.

These contingencies are situated in precise economical, cultural, creative, political, and technical contexts. 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.

How to offer 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, and 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? And how can situated software inform the process of technical writing?