- how to quote propperly an introduction from a book series? (software studies)
- find where to put _code documentation_&_developers_ paragraphs
- find where to put code documentation & developers paragraphs
- elaborate on citations
```
---
How do you choose a particular programming language, a coding paradigm, a development environment, an infrastructure where to run the code, and so on? These are not just technical choices, but rather coding contingencies.
it should stop assuming reader - see natural readers
`
```
### Getting started
`("Getting startled" could also make for a nice title)`
@ -63,32 +63,25 @@ Programming means to deal with picky stubborn machines that don't overlook a sin
Instead...
- lowering barriers
```
lowering barriers
- debugging (p5.js education working group, 2015)
- aesthetic programming
- welcome.js (bridle, 2016)
```
## "Natural" reader
```
- assuming a certain kind of reader - expert - dude
- references:
- programming for the millions (ullman, 2016)
- read the feminist manual (karagianni, 2021 )
- bro culture ? ? ?
(could be the transition from previous section)
(could be the example with evvvvil help patches)
vvvv is a visual programming language that offers an agile approach to prototyping, adoperated especially in the context of interaction design. It's focused on rapid and iterative work of fine tuning, necessary when dealing with real time inputs, such as sensors, live data, or human interaction.
vvvv is a visual programming language
used esp with interaction design
fine tuning, iterative process
help patches
- refer to a specific cultural niche ? see ullman, even tho need to counter balance with other examples
- manuals often address just male developers
- often documentation doesn't offer entry points for beginners, or a sense of direction, this esp a problem with hypertexts
```
vvvv is a visual programming language that offers an agile approach to prototyping, adoperated especially in the context of interaction design. It's focused on rapid and iterative work of fine tuning, necessary when dealing with real time inputs, such as sensors, live data, or human interaction.
@ -18,7 +18,7 @@ There could be several approaches for making worlds around software. Here are so
These labels are open and loose, overlapping and not mutually exclusive, temporary and on the move. They are meant to change, to expire fast, and going bad even faster: they require continuous treatments and repeated efforts. That's why I'm naming them all after the _re_ prefix: to aknowledge their being in progress, second hand again, already contaminated. Borrowed by friends and foes, that had borrowed themselves from someone else. One should diffidate of these categories because they're instable. Nonetheless, they offer ways to visualize different strategies to create worlds around software.
