|
|
|
|
@ -268,17 +268,30 @@
|
|
|
|
|
|
|
|
|
|
- ok plan is to start these and then see what happens
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## round 5
|
|
|
|
|
|
|
|
|
|
- to make your code run faster
|
|
|
|
|
|
|
|
|
|
- what is it?
|
|
|
|
|
- a series of small pubblications
|
|
|
|
|
- readme files
|
|
|
|
|
- for code developed around the soupboat
|
|
|
|
|
- with 3d printed legs
|
|
|
|
|
- to make them run faster
|
|
|
|
|
|
|
|
|
|
- optional: could include thesis
|
|
|
|
|
|
|
|
|
|
- imagine it as an ecosystem
|
|
|
|
|
- with different zones
|
|
|
|
|
- soupboat
|
|
|
|
|
- wiki
|
|
|
|
|
- git
|
|
|
|
|
- browser
|
|
|
|
|
- real people
|
|
|
|
|
|
|
|
|
|
- every code is situated different in this ecosystem
|
|
|
|
|
- in ways that are too complex to explain precisely outside the documentation
|
|
|
|
|
- but can be depicted easily using a mapping approach
|
|
|
|
|
- it also does not need to be super precise
|
|
|
|
|
- and can be playful enough to lure people in
|
|
|
|
|
- while at the same time offer an intuitive way of how these software are oriented in the world
|
|
|
|
|
|
