Ah yes, yet another attempt to decrypt the Rosetta Stone of #coding - "literate programming." 📚💻 A literary masterpiece where everyone pretends to understand #Knuth, while secretly just hoping the comments make the code run faster. 🤦♂️ Spoiler alert: It’s like Shakespearean sonnets but for the terminally nerdy.
https://pqnelson.github.io/2024/05/29/literate-programming.html #literateprogramming #humor #techliterature #nerdculture #programmingjokes #HackerNews #ngated
#literateprogramming
What even is "literate programming"?
https://pqnelson.github.io/2024/05/29/literate-programming.html
#HackerNews #literateprogramming #programming #concepts #tech #education #coding #insights
Ayer presenté en LatinR 2025 un paquete de R llamado taxnames, que sirve para insertar nombres científicos de organismos en documentos de R Markdown o Quarto. Desarrollé este paquete para ampliar las capacidades de taxlist y facilitar la conexión entre bases de datos taxonómicas y documentos taxonómicos o de biodiversidad.
Si te interesa este tema, echa un vistazo a la presentación: https://www.youtube.com/watch?v=Cg27K-hdaQ0&list=PL9-E3cL2KgKnHT6jP17fZozEN-KVTWp_m&index=2
#rstats #LatinR2025 #taxonomy #environment #biodiversity #literateprogramming
My contribution to this month's Emacs Carnival, *An ode to org-babel*, as hosted by @donaldh.
https://www.homepages.ucl.ac.uk/~ucecesf/blog/20251112.html
#Emacs #EmacsCarnival #OdeToOrgBabel #orgmode #DataProcessing #DataAnalysis #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/
@publicvoit @lukascbossert I remember that paper well and it did have impact. At least for me, it gave me the reassurance I needed to go full-on on using org mode for writing my academic papers. So, thank you!
@lukascbossert In 2012, I presented a paper at #iKNOW2012 where I demoed the workflow to generate an ACM whitepaper from one single #Orgmode file + Org-babel + raw data files in CSV format.
Template used: https://github.com/novoid/orgmode-ACM-template together with Tom Dye.
This might be irrelevant implementation-wise because it would need an update but the workflow idea is still awesome!
The people at the session back then mostly did not get it. I probably failed to transmit the idea because they asked specific questions about the demo example data which was just lorem ipsum to me. 😉
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
I wrote a little about "literate programming" used to implement proof assistants, mostly about the "literate programming".
#LiterateProgramming #ProofAssistant #Logic #Mathematics
https://thmprover.wordpress.com/2025/09/16/literate-implementations-of-proof-assistants/
@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
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
Does this sort of thing count as an intrusive thought?
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
@ArneBab Looking good, always nice to look into people's #LiterateProgramming
Of course I should have assumed you would be in the orgmode camp.
Its nice to imagine it being in the wasm - even when Guile doesnt have everything already in place knowing theres a commitment from others to implement from that community is a strong assurance.
You should add a reference to the repo on that webpage however.
In the end I resorted to split presentation and calculations.
A simple #javascript copied and pasted into one of the many online engines. https://ni18-in.github.io/ni18/simple-javascript-compiler appears to be especially lightweight. As many others I am sure.
Console output copied and pasted in to the .rtf file for sharing. Plotting with the aide of @datawrapper .
It feels odd having the app for #LiterateProgramming in the form of a web browser, javascript engine and all, and not being able to use it.
I am sharing with someone a .rtf file with simple calculations and explanatory text. It is mostly edited on #iPad and read from #iPhone. I modify calculations now and then and update the results. All within the same file. So there’s no spreadsheet function involved. Just me and a plain old calculator.
Anyone knows a lightweight and simple #literateProgramming #notebook which runs on mobile? As an alternative something my portable router could run.
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.
#programming #systemsProgramming #software #commonLisp #sitcalc #emacs #eepitch
https://screwlisp.small-web.org/complex/my-eepitch-send-actions-and-the-situation-calculus/
I relate #Sandewall's call for situation calculus actions and the shared environment / database to be moved into the kernel viz my #literateProgramming emacs useage.
People always said emacs /was/ the operatingsystem, didn't they.
Particularly, computer programs various send requests for actions to the emacs server where they are also seen playing out at they actually happen in real time.
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst