This is really fun. Thanks for sharing. When I was in grad school, Knuth’s literate programming were influential to me. Whenever I code, I think just as much about the people reading the code as I do about the correctness of the code.
Your system really seems to enable both at the same time.
Thanks! I figured that since people on substack are likely more inclined to writing, literate programming would be of interest. I didn't find out about Literate programming until after college, but I really got into it. I would love to see it gain more popularity.
What I took from literate programming isn’t so much a specific set of tools, but really a way of thinking about programming that centers communication to other humans as a top goal. Good tooling for this is awesome, too.
I am noticing that in the mobile version of this article code sections aren't displaying properly. If you are running into that problem, use the desktop version of the web page to see the code sections clearly.
I'm not too familiar with Quarto, but looking at it quickly online it does look really similar. Organic Markdown has the Jupyter style workbook stuff but adds Donald Knuth style reference syntax as well. I am going to put up some more documentation to explain that aspect of it soon.
This is really fun. Thanks for sharing. When I was in grad school, Knuth’s literate programming were influential to me. Whenever I code, I think just as much about the people reading the code as I do about the correctness of the code.
Your system really seems to enable both at the same time.
Thanks! I figured that since people on substack are likely more inclined to writing, literate programming would be of interest. I didn't find out about Literate programming until after college, but I really got into it. I would love to see it gain more popularity.
What I took from literate programming isn’t so much a specific set of tools, but really a way of thinking about programming that centers communication to other humans as a top goal. Good tooling for this is awesome, too.
I am noticing that in the mobile version of this article code sections aren't displaying properly. If you are running into that problem, use the desktop version of the web page to see the code sections clearly.
Is this like a Quarto document except with a lot of steps?
I'm not too familiar with Quarto, but looking at it quickly online it does look really similar. Organic Markdown has the Jupyter style workbook stuff but adds Donald Knuth style reference syntax as well. I am going to put up some more documentation to explain that aspect of it soon.
There's a good explanation of some of that in the README for the GitHub project: https://github.com/adam-ard/organic-markdown
Allright, thanks for looking into it ;)