Yes. There is never one view of a program, but multiple architectural views. Literate programming in the sense of documenting a program like a monograph is too

Yes. There is never one view of a program, but multiple architectural views. Literate programming in the sense of documenting a program like a monograph is too one-dimensional. I would like to see an emphasis on test inputs/outputs instead. Given all the Test vectors the actual code becomes irrelevant. It seems that we focus on the code because it used to be the bottleneck, plus it’s the densest piece of information in the system…and takes less paper to print. In a world where modules must be constantly integrated, I’d rather read the test traces than the code itself. Good programmers can simulate the code in their heads and internally generate the traces…but presumably the point of literate programming should be to remove that burden from the reader.