The practice of pair programming involves two developers coding together on the same machine, with distinct roles. The <em>driver</em> writes the actual code, while the <em>navigator</em> 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.
<p>experiments with pair doc writing together with chae for the <ahref="https://git.xpub.nl/manetta/flask-example/src/branch/documentation">flask example repo</a>, that led to a more welcoming and vernacular way of writing</p>
<p>Documentation is not just for beginners, is a code companion. One never stops reading. Both newcommers and experienced developers alike read documentation, that meets them in different moment of their programmer lives, from the <em>hello world</em> to the <em>how to uninstall</em></p>
<p>when pairing reading make sense? which kind of situations?</p>
<p>im struggling because all of these things are activities and not objects and this cause me disconfort </p>
<li>one read, the other document the reading process: keeping track of the screen walk, annotating resources, drating a map of where knowledge has been found</li>
