@ -32,3 +32,20 @@ Documentation brings an understanding on software by disclosing its magic. It re
Documentation is a space that interfaces between the code, the user, the developer, and the world. A space where to welcome different voices: not just engineers, not just experts, not just dudes. A space to acknowledge the massive labor of care besides technicalities, often marginalized by coding culture.
A surface that could host principles in close contact with algorithms, letting them entangle and shape each other. A way to orientate our instruments towards "non-extractive relationships, but in the meantime, being accountable for the ones they are complicit with." (A Wishlist for Trans\*feminist Servers, 2022)
---
## Homework
### Software documentation
While I do think that this research relates with technical writings in a broad sense, the approaches and methods proposed here are mostly informed by the worlds around coding documentation. When reading, please bind the terms software, application, program, etc. to code. Software documentation? Code documentation. The perspective of this text is more aligned to the docs of [ImageMagick](https://imagemagick.org/index.php) than to the ones of [GIMP](https://www.gimp.org/). The concepts of worlding, political aesthetic, and critical thinking apply to all kinds of manual. Nonetheless, it's probably going to be way easier to read this if you picture it figuring documentation for code and programming.
### For developers
I would like to blame the Capitalist Realism we are surviving in for this (probably not the case). For people to get identified with their profession. And the other way around: for activities being doomed by the aura of professionalism. Who is a developer? One who programs for a living or one who lives for programming? (based)
Here a developer is someone tinkering with code. 1. one choose to participate 2. Expertise doesn't matter. Documentation is both a beginner and experienced user-friendly surface.
