so literate programming became known to knuth as a web. I agree.
In particular, when trying to decide where to place code, it often goes in multiple places. For example, in a CRUD, we have form -> server -> db -> page so does one put the code for the db in with the db code or with the particular sequence. It becomes an issue when one is trying to deal with changes on either end. So maybe the solutions is both. Have a graph of relations, one relation being the flow, one being the function, near kin, etc. And so a web of stuff.
so literate programming became known to knuth as a web. I agree. In particular, when trying to decide where to place code, it often goes in multiple places. For example, in a CRUD, we have form -> server -> db -> page so does one put the code for the db in with the db code or with the particular sequence. It becomes an issue when one is trying to deal with changes on either end. So maybe the solutions is both. Have a graph of relations, one relation being the flow, one being the function, near kin, etc. And so a web of stuff.