@ -39,10 +39,18 @@ A surface that could host principles in close contact with algorithms, letting t
### 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.
The concepts of worlding, political aesthetic, and critical thinking can be applied to all sorts of technical manuals. The approaches and methods explored in this thesis although are mostly informed by practices related to code documentation. While reading, please bind the terms software, application, program, etc. to code. Software documentation? Code documentation.
`not sure about next paragraph ? find accessible examples, at least a couple`
The perspective of this thesis is more aligned to the docs for [ImageMagick](https://imagemagick.org/index.php) than to the ones for [GIMP](https://www.gimp.org/).
### For developers
Another term to dismantle here is _developer_. By stripping down every trace of professionalism and formal education, this text is meant for everyone that wants to tinker with code. No matter at which intensity, nor distance, nor experience. No matter if for work, if for fun, if for learning. No matter if actively involved in the development or maintainance or from the user perspective. Here the word _developer_ is used like a labcoat that one has to wears
---
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.
