←back to thread

88 points joecobb | 1 comments | | HN request time: 0.001s | source
Show context
em500 ◴[] No.46180399[source]
This essay seems to be missing the main primary references for literate programming:

https://www.cs.tufts.edu/~nr/cs257/archive/literate-programm...

https://www-cs-faculty.stanford.edu/~knuth/lp.html

Knuths intention seems clear enough in his own writing:

Literate programming is a methodology that combines a programming language with a documentation language, thereby making programs more robust, more portable, more easily maintained, and arguably more fun to write than programs that are written only in a high-level language. The main idea is to treat a program as a piece of literature, addressed to human beings rather than to a computer.

and

Let us change our traditional attitude to the construction of programs: Instead of imagining that our main task is to instruct a computer what to do, let us concentrate rather on explaining to human beings what we want a computer to do.

replies(5): >>46181093 #>>46181151 #>>46181215 #>>46184360 #>>46185842 #
rhdunn ◴[] No.46181215[source]
In a way this is what notebooks are for Python and other languages. They mix documentation and code such that you can run that code and inspect the output. See for example the pytorch tutorials.
replies(2): >>46181278 #>>46181329 #
1. electroglyph ◴[] No.46181278[source]
or all the unsloth notebooks