- with a clear structure the simulation can be more heterogeneous
- aggregate materials and references
- no need to be SUPER discoursive
- could be evocative
- think are.na channels on instagram
- intro as a readme file
- Could be interesting to read What the Dormouse Said
```
## SETUP
## Setup
Notes:
- simulation as writing machine
- outline simulation key points:
- Suspension of judgment
- Discrete temporality
- Partiality
- Orientation
- aknowledge software as cultural object
- and propose software documentation as a surface
- to renegotiate the making of software
- to create entry points
- to question who gets to participate
- and propose software documentation as an entry point
- to renegotiate the context around software
- plan
- Outline the structure of the simulation
---
@ -79,24 +65,20 @@ Using the simulation as a writing machine we can articulate these CC with some b
This procedure helps us to think about software as cultural object. Something "deeply woven into contemporary life –economically, culturally, creatively, politically– in manners both obvious and nearly invisible." (Software Studies, 2009), and not just as technical tool existing in a vacuum.
## REQUIREMENTS
[structure of the simulation]
[software documentation as entry point]
Notes:
## Requirements
- need things to simulate
Notes:
- not only
- the software and hardware circumstances of code (Marino, 2020)
- but also
- the relations with _non-code entities_ (Mackenzie, 2006)
- actors
- programming languages
- use cases
- Generate data
- possible references to build the dataset
- Weathering Software Winter (100R)
- Close to the Machine, Life in Code (Ulman) (focus on episode)
- Pattern of Software, (Gabriel) (focus on episode)
@ -108,25 +90,14 @@ Notes:
- Python and diataxis?
- SI16?
---
first we need things to simulate:
- actors
- programming languages
- use cases
the simplest simulation
aha how do we define actors?
- Generate data
it reminds me of this OOO statement:
objects sink into themselves
that is an effective and graphical way to describe technical reference pages and auto generated API specs, with nested nested nested layers of list.
- Actors
- Programming languages
(brief overview?)
- Use cases
to avoid that
let's define actors not for what they are but for what they do
(that is fun bc then i wrote grandma, that means functional grandma, that means not someone that has grandchildren but someone that does grandparent functions ??? ok this is not fun anymore and i am sorry)
---
- actors
@ -137,16 +108,17 @@ let's define actors not for what they are but for what they do
- teacher
- student
- grandma
- sailor
- programming languages
- c
- javascript
- python
- vvvv
- pure data
- haskel
- rust
- redstone circuits
- assembly
- use cases
- research
@ -154,6 +126,7 @@ let's define actors not for what they are but for what they do
- art
- fun
- activism
- survival
then we need to combine thigs from the three categories
