@ -51,86 +51,112 @@ The critical and theoretical research will be weaved around the actual documenta
Strategies to share workloads and collaboration
Strategies to share workloads and collaboration
Strategies to take care of shared piece of software. -->
Strategies to take care of shared piece of software. -->
1. Coding Contingencies _(2000)_
## 1. Coding Contingencies
Situate software as cultural object and propose documentation as a surface to explore it.
1. Context around software, besides technicality _(500)_
_(2000)_
- Refer to software studies
2. Introduce issues around software _(1000)_
Outline a map of critical issues related to software culture, grouping them in three main flavours:
1. Biased and hostile environments
Situate software as cultural object and propose documentation as a surface to explore it.
- Toxic masculinity, encoded chauvinism, western monoculture
2. Evergrowing complexity
- Intimidating learning curve, disproportion of means, mistification
3. The universal solution™
- Techno solutionism, gray tech, ideology
3. Propose documentation as a surface to address these issues _(500)_
### 1.1 Context around software, besides technicality
1. Welcoming diverse knowledges
2. Lowering barriers and create entry points
3. Orientate software in the world
2. Documentation as an interface _(3000)_
_(500)_
Aknowledge documentation as crossroad for different actors, as intersection between code, machines, developers, users. Articulate it as a vantage point from where to reason about software.
0. Define software documentation
Refer to software studies
- _What is written?_
### 1.2 Introduce issues around software
1. From printed manuals to discord servers _(small historical overview)_
- Here not focusing on one specific catch-all format
Outline a map of critical issues related to software culture, grouping them in three main flavours:
- rather to a form of care (for users, for software, for context)
- in the context of situated software
1. Welcoming diverse knowledges
1. **Biased and hostile environments**
- Toxic masculinity, encoded chauvinism, western monoculture
2. **Evergrowing complexity**
- Intimidating learning curve, disproportion of means, mistification
3. **The universal solution™**
- Techno solutionism, gray tech, ideology
- _Who is writing?_
### 1.3 Propose documentation as a surface to address these issues
- How does development and technical writing interact?
_(500)_
- Is the technical writer a subaltern position in the industry of software development?
- Who gets to write, and who is forced to?
- No one wants to write documentation, or pay someone to do it
- Documentation as a form of care
- _Who will read?_
1. Welcoming diverse knowledges
_Who is addressed?_
2. Lowering barriers and create entry points
3. Orientate software in the world
- Assuming a certain kind of reader (often male, often white, often with formal education)
## 2. Documentation as an interface
- Read the feminist manual (Karayanni, 2021)
- Programming for the millions (Ullman, 2016)
2. Lowering barriers and create entry points
_(3000)_
- _Who can access?_
Aknowledge documentation as crossroad for different actors, as intersection between code, machines, developers, users. Articulate it as a vantage point from where to reason about software.