@Eduardo Mercovich (él)

I sort of had it in mind that it might be in chapters (or possibly modules?)  with the code relevant for that chapter in there  too.

The point of literate programming is that there isn't a distinction between 'code' and 'documentation'.  I realise your thesis goes beyond code and documentation about the code, but I wonder whether the same line of thought might still apply: perhaps the discursive thesis, the code, the code's documentation, the data, etc. all belong with one another, on a topic or chapter basis?

As I don't have a very concrete suggestion but just some floating ideas, I think my advice is still the same: keep it as one file for now and work it out later.  A division that makes sense may arise as you & your collaborators work with it more — let the cowpaths emerge!

I think one file will leave your mind more open to other alternatives too.  Generally speaking if you don't have a good basis to make a decision, and there's no real reason to make it right now, it's better to just defer it.

However, I don't think anything very much will go wrong if you decide you like the idea of splitting it into code and non-code. You can always change your mind later.

# tem25 # literateprogramming