The practice of pair programming involves two developers coding together on the same machine, with distinct roles. The driver writes the actual code, while the navigator reviews each entry along the way. Roles are often switched. Developers with similar or different experience can collaborate in pair programming, with benefits for both parts.
Could the concept of pair programming be applied to documentation?
pair documentation writing: one writes and the other provides perspective, such as reviewing if there are parts that are not clear
pair documentation reading: one read and the other ???
experiments with pair doc writing together with chae for the flask example repo, that led to a more welcoming and vernacular way of writing
what could it mean to read documentation in pair?