What even is "literate programming"?

https://pqnelson.github.io/2024/05/29/literate-programming.html

#HackerNews #literateprogramming #programming #concepts #tech #education #coding #insights

Really enjoying this month’s #Emacs Carnival on #orgmode — especially the focus on #orgbabel!
Huge thanks to @donaldh for curating the topics.

For me, #orgbabel is where documentation, data, and computation truly meet — it turns notes into living, reproducible workflows.

I’ve written down why I think org-babel is a *ROOT technology*:
https://lukascbossert.de/posts/org-babel/

#Emacs #ROOT #LiterateProgramming

Really enjoying this month’s #Emacs Carnival on #orgmode — especially the focus on #orgbabel!
Huge thanks to @donaldh for curating the topics.

For me, #orgbabel is where documentation, data, and computation truly meet — it turns notes into living, reproducible workflows.

I’ve written down why I think org-babel is a *ROOT technology*:
https://lukascbossert.de/posts/org-babel/

#Emacs #ROOT #LiterateProgramming

Resilient technologies aren’t retro—they’re ROOT: Robust, Open, Ongoing, Time-tested. In RDM, text-first + small, composable tools beat opaque stacks. Emacs/Org(-babel) for literate workflows & provenance; Makefiles declare rebuilds; CLI atoms—curl, sed, awk, grep, diff, tar, rsync, cron, SQLite—keep steps inspectable, portable, rebuildable. DOI: https://doi.org/10.5281/zenodo.17157588 — Feedback welcome!

#ROOT #ResilientTech #Emacs
#OrgMode #RDM #NFDI
#FAIR
#Reproducibility
#literateprogramming
#BoostOK

The meta poster frames the concept: clarity + openness → resilience. It traces the lineage from Knuth’s Literate Programming to Org-mode and NFDI practice, and introduces the ROOT badge as a compact signal for robust, open, ongoing, time-tested tools. It also spotlights resilient stalwarts often hiding in plain sight—find, LaTeX, perl, rsync, SQLite—showing why they remain reliable RDM building blocks.
#ResilientTech #LiterateProgramming #OrgMode #RDM #NFDI #FAIR https://doi.org/10.5281/zenodo.17157588

Main poster maps long-lived tools to the research-data life cycle (Plan → Produce → Analyze → Archive → Access → Re-use). Emacs/Org for provenance, Make for rebuilds, curl/sed/grep/diff for intake & checks, awk for tables, cron for timing, tar/rsync for packaging/sync, plus SQLite/LaTeX/find. Pipelines you can re-run years later. Feedback welcome! #ROOT #ResilientTech #RDM #NFDI #Emacs #orgmode #literateprogramming #OpenScience #tools #researchdatamanagement
https://doi.org/10.5281/zenodo.17157588

Resilient technologies aren’t retro—they’re ROOT: Robust, Open, Ongoing, Time-tested. In RDM, text-first + small, composable tools beat opaque stacks. Emacs/Org(-babel) for literate workflows & provenance; Makefiles declare rebuilds; CLI atoms—curl, sed, awk, grep, diff, tar, rsync, cron, SQLite—keep steps inspectable, portable, rebuildable. DOI: https://doi.org/10.5281/zenodo.17157588 — Feedback welcome!

#ROOT #ResilientTech #Emacs
#OrgMode #RDM #NFDI
#FAIR
#Reproducibility
#literateprogramming
#BoostOK

@a href="https://social.coop/@edumerco" target="_blank" rel="nofollow noopener" 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

What else can I share to better describe the thesis? Some parts that are not clear?

While #orgmode does 85% out of the box (#LiterateProgramming, tagging, counting, writing, exporting, even interacting with #gnuplot, etc.) #elisp is needed to do some of this calculations, ordering and grouping... :)

[end] #tem25

Dear Emacsers.
I need some help w/ #elisp for my #LiterateProgramming + #ReproducibleResearch thesis (an exploration of meaningful abilities to operate outside academia).
I'd like it as completely self contained in -and sustained by- #Emacs (yes, I'm a geek and I'm proud) as possible and, while going forward, I've found my #elisp fu limiting.
Can anyone share some time to help me with this thesis and show the power of Emacs and #FreeSoftware? I'd gladly share my abilities back.
1e^3.Thxs

I went through @compudanzas uxn tutorials once, had fun, and forget everything again. So I did it again, but this time I tried to make some literate programming style notes about all the different aspects I'm picking up. I'm through with my second attempt and I have to say that it was worth the effort. At least the basics stuck now (or so he hoped...)

The notes can be found here but I haven't cleaned up anything yet. I'm pretty sure I have some conceptual mistakes in there as well. The format is also not very consistent along the notes, since I lost patience with myself at times.

https://codeberg.org/thgie/literate-uxn

#uxn#LiterateProgramming

I went through @compudanzas uxn tutorials once, had fun, and forget everything again. So I did it again, but this time I tried to make some literate programming style notes about all the different aspects I'm picking up. I'm through with my second attempt and I have to say that it was worth the effort. At least the basics stuck now (or so he hoped...)

The notes can be found here but I haven't cleaned up anything yet. I'm pretty sure I have some conceptual mistakes in there as well. The format is also not very consistent along the notes, since I lost patience with myself at times.

https://codeberg.org/thgie/literate-uxn

#uxn#LiterateProgramming