It&#x27;s called &quot;literate programming.&quot;<p>I&#x27;m embarrassed of the state of this thing, but I think I&#x27;d be remiss if I didn&#x27;t link to <a href="https:&#x2F;&#x2F;willshake.net&#x2F;about" rel="nofollow">https:&#x2F;&#x2F;willshake.net&#x2F;about</a><p>It&#x27;s a graph of a system based (almost) entirely on documents.  The documents create the documents.  The documents create the graph.  And of course, the documents contain the code.<p>I can&#x27;t make enough disclaimers about how rough the documents are, and even the graph is starting to collapse under its own weight.  But I think it gets the idea across.  If I&#x27;ve learned one thing, it&#x27;s that this style of programming---where you&#x27;re forced to document as you go---is extremely work-intensive.