Literate Programming in the Large

Channel:Next Day Video · Length:35:58 · Published:2013-06-27 · Views:17906

Watch on YouTube

Summary

Timothy Daly, an original author of the Axiom computer algebra system, talks about turning a large Common Lisp codebase into a literate program. He argues code should be written as readable manuals, and the talk was given at Write the Docs 2013.

Why HN recommends it

HN recommends it in literate programming threads as a rare look at applying the idea to a huge, complex codebase, though some find it meandering.

well worth watching: it talks about real, huge comolex systems, and how lp can help bring them back under control — HN, 2016

Functional programming · Software practice, open source & careers

Subtitles (excerpt)

and while they're they're playing with that um I'm here to set the the mood I'm here as an evangelist okay uh so if you're want your company to change uh you probably want to have me come in and sing the song I'm here to tell you that first of all you're doing it wrong the second thing to tell you is you're Godlike figures and your company doesn't know it yet okay um obviously I'm not a Godlike figure because I can't make my huh all right we've lost it um pull it out let me just uh do my slides as I as though they're local this is going to make it somewhat more challenging okay I can dance I don't even have my slides all right I'm here to talk to you about a a uh project called ax axium is a computer algebra system um and uh I worked on it uh when I was at IBM research it was a an Innovative system it was the first general purpose computer algebra system uh it did the annoying things like doing your uh equations that you used to have in high school and it does uh it is one of the largest computer rber systems in the world we worked on it for quite a few years uh it had about 300 people it was about a $42 million project it ran out for 21 years uh at one point rean cut the uh funding for the federal labs and when he cut the funding the IBM

On Hacker News

"Programs should be written for people to read, and only incidentally for machines to execute." (Structure and Interpretation of Computer Programs" by Abelson and Sussman) The idea is that you write a "Book" and the program is extracted, from the book. Literate Programming Wikipedia: [LINK] A nice talk about it: [VIDEO] — elviejo, 2017-05
There's a (somewhat rambling, but interesting) talk on the effort to rewrite the lisp symbolic math system Axiom[a] as a literate program (spanning several books) - precisely in order to make it possible to refactor and maintain the code: "Literate Programming in the Large": [VIDEO] [a] [LINK] — e12e, 2016-07
I think there are two sound approaches to communicating complex systems between humans (which is the main goal here, a computer might be a bit slow compiling 200M LOC - but the real problem is that no human can read that much code, let alone understand it): 1) Write documentation that is also code. That is the idea of literate programming. I recently came across: "Literate Programming in the Larg… — e12e, 2016-05
I found this talk about re-structuring and bringing back to life a 1.2 MLOC lisp codebase with classical LP interesting (it's a bit meandering, but INHO well worth a watch): "Literate Programming in the Large": [VIDEO] The reorganization is still ongoing, as can been seen at: [LINK] — e12e, 2016-05
I like Tim Daly's viewpoint that we shouldn't just be writing code , but we should write manuals - giving high level overviews of our problems and specifying their implementation details inside the manuals. His talk "Literate Programming in the Large"[1] covers why. The example he gives in his talk is the Axiom algebra system[2], which was revised to use literate programming style - the source co… — sparkie, 2014-04

Related videos