Thanks for including the link to your paper[1] in the README. I saved it in my Zotero library and am looking forward to reading it.
Do you have any thoughts or experience with literate programming? What about the role of Docable, versus choosing PDF as the medium for your own paper, versus something like this[2] sort of thing?
Living papers are useful vision, but it will take a long way to get there.
Even notebooks still are problematic, for example, this study found that only 25% of Jupyter notebooks could be executed, and of those, only 4% actually reproduced the same results.
One compromise is to evaluate the paper separate from it's artifacts, which are reviewed for availability, reproducibility, and reusability. In software engineering conferences, this is becoming a standard, and while there is a huge burden for reviewers to evaluate these things, I think it does take us in the right direction. So in this case, we also submitted our paper for evaluation for its artifacts.
Thanks for including the link to your paper[1] in the README. I saved it in my Zotero library and am looking forward to reading it.
Do you have any thoughts or experience with literate programming? What about the role of Docable, versus choosing PDF as the medium for your own paper, versus something like this[2] sort of thing?
1. http://chrisparnin.me/pdf/docable_FSE_20.pdf
2. https://csarven.ca/this-paper-is-a-demo