kamo
/
tag
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

03 pair

Browse Source
main
km0 1 year ago
parent be72324af3
commit 81d50ec1a7
3 changed files with 54 additions and 4 deletions
Show Stats Download Patch File Download Diff File

43
03/index.html
Unescape Escape View File

@ -0,0 +1,43 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>03 - Pair</title>
<link rel="stylesheet" href="/style.css">
</head>
<body>
<header>
<h1>doc doc doc</h1>
<div class="sub">documenting code documentation</div>
<div class="info">hello! welcome. this is an archive to navigate trough documentation practices</div>
<div class="attempt">pair programming and pair reading.</div>
</header>
<section>
<div class="prompt">
<p>
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>
<p>
Could the concept of pair programming be applied to documentation?
</p>
<p>pair documentation writing: one writes and the other provides perspective, such as reviewing if there are parts that are not clear</p>
<p>pair documentation reading: one read and the other ??? </p>
<p>experiments with pair doc writing together with chae for the <a href="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>what could it mean to read documentation in pair?</p>
</div>
</section>
</body>
</html>

15
index.html
Unescape Escape View File

@ -26,6 +26,8 @@
there is no clear path / a practice to learn / shared practice personal practice
</div>
</header>
@ -51,10 +53,10 @@
<ul>
<li> - to infiniltrate technical world</li>
<li> - inject contexts into code</li>
<li> - entry points for people to participate and learn in coding</li>
<li> - entry points to know and participate in these contexts</li>
<li> to infiniltrate technical world</li>
<li> inject care into code</li>
<li> entry points for people to participate and learn in coding</li>
<li> entry points to know and participate in these contexts</li>
</ul>
</div>
@ -67,6 +69,11 @@
<ul>
<li><a href="01">01 - Pathways</a></li>
<li><a href="02">02 - Openings</a></li>
1.1 pathway with thesis
2.1 openings v2 - different ways to intend openings (could be different prototypes)
3. reading ? pairs reading?
</ul>
</section>

0
notes.md
Unescape Escape View File

Write Preview
Loading…
Cancel
Save