Yeah, it just seems to me that wonderfully written literate documentation would be poorly organized software, and wonderfully organized software would be poorly organized documentation.<p>I guess what I mean by that is that as software scales out, your code will be more along the lines of &quot;do this logic whenever this function&#x2F;method happens to be invoked&quot;.  So it would be great for documenting the workings of a function&#x2F;method, but it would be poor for actually documenting the lifecycle of a logic path, like the lifecycle of a request.  I certainly wouldn&#x27;t have one file where I handle a request, do some business logic, and interact with a database, even though that is how you might document a lifecycle the request.