chapter 1 as simulation
parent
785ad61e64
commit
57cea6eb2d
Binary file not shown.
@ -0,0 +1,80 @@
|
||||
simulation, chapter 1, contingencies
|
||||
|
||||
chapter 1 is not a written as a text, but as a simulation.
|
||||
coding contingencies is a dwarf-fortress-ish take on how different characters got to code.
|
||||
so instead of writing my bio that begins like "ah, i always approached things from the other side, probably because for us* this everything is new" and then continue on how i got into coding from the arts (not a real developer!), and into codings as a job (not a real artist!), and bla bla.
|
||||
|
||||
but here we are doing a simulation, a software fortress, also known as computer.
|
||||
(context: dwarf fortress is a roguelike game that lets you explore incredibly detailed and rich simulations) (there are funny videos about it, the most famous is a bug report about dead cats in a tavern because of simulated alcohol on their paws that they were ingesting while cleaning themselves)
|
||||
|
||||
so back again
|
||||
chapter 1 is not written as a text, but as a simulation.
|
||||
|
||||
|
||||
software contingencies
|
||||
the simulation
|
||||
|
||||
first we need things to simulate:
|
||||
|
||||
- actors
|
||||
- programming languages
|
||||
- use cases
|
||||
|
||||
the simplest simulation
|
||||
|
||||
aha how do we define actors?
|
||||
|
||||
it reminds me of this OOO statement:
|
||||
objects sink into themselves
|
||||
|
||||
that is an effective and graphical way to describe technical reference pages, or auto generated API specs, with nested nested nested layers of list.
|
||||
|
||||
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
|
||||
- web designer
|
||||
- interaction designer
|
||||
- graphic designer
|
||||
- musician
|
||||
- teacher
|
||||
- student
|
||||
- grandma
|
||||
|
||||
- programming languages
|
||||
- javascript
|
||||
- python
|
||||
- vvvv
|
||||
- pure data
|
||||
- haskelz
|
||||
- rust
|
||||
|
||||
- use cases
|
||||
- research
|
||||
- work
|
||||
- art
|
||||
- fun
|
||||
- activism
|
||||
|
||||
then we need to combine thigs from the three categories
|
||||
|
||||
00 web designer, rust, activism
|
||||
01 teacher, haskel, work
|
||||
02 grandma, rust, fun
|
||||
03 interaction designer, vvvv, art
|
||||
04 musician, pure data, work
|
||||
05 musician, python, research
|
||||
06 student, python, art
|
||||
07 student, javascript, work
|
||||
08 student, javascript, fun
|
||||
09 graphic designer, haskel, research
|
||||
|
||||
side note
|
||||
NOT is the series on theory in italian by NERO
|
||||
their first pubblication was Capitalist Realism, Mark Fisher and it was a declaration of intents.
|
||||
at some point every first is a declaration of intents.
|
||||
but is that so also in random generated series?
|
||||
|
||||
|
||||
|
Loading…
Reference in New Issue