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.
46 lines
1.1 KiB
Markdown
46 lines
1.1 KiB
Markdown
# Notes to the self
|
|
|
|
## Plan for first draft deadline (20/02/2023)
|
|
|
|
- intro good
|
|
- first chapter 60% good 40% outline
|
|
- second & third chapters outline and refs
|
|
- update readme.md
|
|
|
|
|
|
## 9/02 Buddies session with Alex & Marloes
|
|
|
|
- Intro:
|
|
- define that we are talking about code documentation
|
|
- define who is addressed when we say "developer"
|
|
- explicit structure of the chapters for last three paragraphs
|
|
|
|
|
|
## Old notes
|
|
|
|
- be a mean to explore these contingencies?
|
|
|
|
- coding contingencies
|
|
- software studies
|
|
- documentation to address issues
|
|
1. Welcoming diverse knowledges
|
|
2. Lowering barriers and create entry points
|
|
3. Orientate software in the world
|
|
- **practical example!!!**
|
|
|
|
- be an interface between different knowledges?
|
|
|
|
- interface between code, developer, world
|
|
- post meritocracy manifesto
|
|
- trans\*femminist server whishlist
|
|
|
|
- be an ideal surface to build worlds?
|
|
|
|
- the screenless office
|
|
- ian cheng
|
|
|
|
- be a device to trigger different kinds of economy around situated software?
|
|
- 360 degrees of proximity
|
|
|
|
|