Found in 4 comments on Hacker News
wtetzner · 2018-09-05 · Original thread
And turned the source code of the tooling into a book!

dfan · 2017-02-12 · Original thread
The Stockfish chess engine:

I learned a ridiculous amount from reading the source code to TeX ( but it is written in a very 1970s style.

microtherion · 2016-12-20 · Original thread
It's a bit old, of course, but TeX: The Program is still a fascinating read because of the exceptional attention that Knuth has paid to exposition, especially for a program that size. Besides, TeX is still being used after almost 40 years, so it's inarguable that Knuth did some things right.

todd8 · 2016-09-01 · Original thread
Yes, the iPython notebooks are great for reproducible reports. Literate programming, as practiced by Knuth, is a little bit different. The program's output, graphs, tables, etc. isn't intermixed with the text as it is in a Jupyer notebook. A literate program is actually documentation and source mixed together in a web file. Two different programs (tangle and weave) can be run over this literate code. One extracts a (LaTeX) document suitable for publication and the other extracts a program (with all of the documentation stripped out) to be fed into a compiler. The best example I know of is Computers & Typesetting, Volume B: TeX: The Program [1], a 624 page book that is a complete exposition on the TeX program, generated by weave; the same web source run through tangle generates the TeX program itself (the typesetting program upon which LaTeX is built out of TeX macros).

Knuth is a fan of this method of program construction. Of course, he is not only a phenomenal programmer; he is a great writer skilled at explaining complex algorithms and code. I can see why literate programming suits him.


Fresh book recommendations delivered straight to your inbox every Thursday.