_could documentation be a surface to build worlds around software?_ > aknowledge doc importance - software without documentation is invisible - documenting code from different distances > what it should do > what it often does intead how doc - different documentations for different readers probs - who is reading? - not for beginner props - lowering barriers and creting entry points - readme exampless - p5js debug examples ## Software without documentation Software without documentation is invisible. Therefore it is important to document it. Software without documentation tends to slip away, to disappear. Therefore it is important to have some notes on how does it work, how does it tackle the problem to solve. The devil is in the details, and software as well: the translation between human and machine has to be negotiated with all the small specifics of a particular programming language or platform. These specifics make every piece of code alien and peculiar. Tinkering with code is not just knowing by hearth a programming language, but rather having to deal with a lot of different recipes. Opening undocumented code feels like being an ant walking on a big painting. You can see the strokes of a brush, and have an intuition of their direction, but what's missing is an overall idea of how the composition flows. Documentation provides guidance through the bunch of functions and statements that makes software. These guidelines are helpful when sharing programs with others, as well with future selves. They provide an entry into the messy relationship between developers and machine. --- _bonus caption for images:_ Being programming slightly different from cycling, people tend to forget what their code does, and how did it get there. (Maybe because it doesn't involve muscle memory?) Software documentation is a defensive mechanism operated from our past selves to protect the present and future ones. Cuneiform writing and comments. (even though this is cuneiform writing and syntax highlighting) ## Different distances Documentation can happen at different distances from code: directly in source with lines of comment—ignored by the machine, but much appreciated by fellows developers—or it can be printed in books, along with pages of examples and references. Who is writing could be the very same developer or someone else. Writings come with different approaches and intentions, and as response to different needs. Documentation is not just for beginners: it's a code companion. It affects code continously. Even experienced programmers must refer to the docs when first encountering a software. ## Different documentation for different readers Documentation comes in many different forms. Daniele Procida offers a systematic approach to organize this wealth of formats (diataxis.fr, 2017). His framework is built at the intersection of two axis: one goes from theoretical to practical knowledges, while the other from study to work. Here _study_ could be read as _learning_ or _understanding_, while _working_ means getting things done. Another powerful couple of synonims is _receiving_ and _giving_: by combining the renamed axis we can get a glimpse of the flow of knoweldge involved in documentation. ``` practice receiving tutorial theory receiving explanation practice giving how to theory giving reference ``` The structure of dyataxis is useful to navigate through the different needs of a reader, or through different readers at all. So who's reading? ## Not for beginners Documentation that fails to address its reader can result inaccessible and frustrating. ## who is reading? - assuming a certain kind of reader - expert - dude - references: - programming for the millions (ullman, 2016) - read the feminist manual (karayanni, 2021 ) ## lowering barriers and creting entry points - lowering barrier - debugging (p5.js education working group, 2015) - aesthetic programming - readme examples? - Problems with depth (too shallow or too deep) - multiple entry points - different entries make for different knowledges - drawings and memes - welcome.js (bridle, 2016) that brings us to --> welcoming different knowledges