|
|
|
|
# Notes to the self
|
|
|
|
|
|
|
|
|
|
## tutorial with Cristina 29/03
|
|
|
|
|
|
|
|
|
|
Things to talk about:
|
|
|
|
|
|
|
|
|
|
- recap documentation session
|
|
|
|
|
- next session ?
|
|
|
|
|
- documentation archive + tag system
|
|
|
|
|
- sister server 360 degrees for thesis
|
|
|
|
|
- queer motto api for thesis
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## for Jian
|
|
|
|
|
|
|
|
|
|
- https://mermaid.js.org
|
|
|
|
|
- https://asciiflow.com/
|
|
|
|
|
|
|
|
|
|
## Tutorial with Cristina, lecture with Aymeric
|
|
|
|
|
|
|
|
|
|
- lack of documentation is (not) the only problem
|
|
|
|
|
- documentation as gardening, need for constant maintainance
|
|
|
|
|
- see refs in the queque
|
|
|
|
|
- look into gemini protocol for documentation
|
|
|
|
|
- garden library network
|
|
|
|
|
- print a small photo receipt roll for Marloes
|
|
|
|
|
- cultural diffusion vs cultural appropriation
|
|
|
|
|
- tower of babel of technicalities
|
|
|
|
|
|
|
|
|
|
## Aaaaaaaaaaaaaaaaaaaaaaaaaa
|
|
|
|
|
|
|
|
|
|
For research question: developing and sharing tools is important so mention it
|
|
|
|
|
|
|
|
|
|
## Cycling along the river
|
|
|
|
|
|
|
|
|
|
- notes for thesis: cycling along the river, documentation, learning a new language, esolang, exploring different ways of thinking
|
|
|
|
|
|
|
|
|
|
## Revision on structure and late night notes
|
|
|
|
|
|
|
|
|
|
- new intro
|
|
|
|
|
- two flows
|
|
|
|
|
- (chap 02) from close to the mainframe to telescopic writing
|
|
|
|
|
|
|
|
|
|
## Bouldering and secrecy
|
|
|
|
|
|
|
|
|
|
- suckless and bouldering: different levels of documentation
|
|
|
|
|
- documentation as backdoor
|
|
|
|
|
--> but for a different target
|
|
|
|
|
|
|
|
|
|
- stealth
|
|
|
|
|
|
|
|
|
|
- cave paintings
|
|
|
|
|
|
|
|
|
|
## 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
|
