I always understood literate programming as a tool for teaching and not as a tool for writing software. As I've written more and more about code I wrote, I've

I always understood literate programming as a tool for teaching and not as a tool for writing software. As I've written more and more about code I wrote, I've found myself inventing weird ways of making sure the code samples are compilable, runnable and correct. I've done it enough that now I'm considering using a literate programming tool next time. (To be clear, I'm not referring to traditional API documentation with examples. There exist good tools for testing examples without resorting full-hog to literate programming. I am referring to more general prose whose aim is less specific than documenting an API.)