In my view, notebooks are the exact opposite of literate programming, and it's a shame some people seem to think it is its pinnacle instead. The focus on a not

In my view, notebooks are the exact opposite of literate programming, and it's a shame some people seem to think it is its pinnacle instead. The focus on a notebook is the report, not the code. In practice this means that the report structure dictates code structure, not the other way round. By contrast, the focus of literate programming is the code. Any "reporting" done is strictly to enhance the code, and not the other way round. I've seen far too many codebases that should have been "code generating a report" reverse that logic and implemented as notebooks instead, in the expectation that the underlying code can simply be exported from the report. Good luck if you need to work on someone's code of that kind. It's its own special kind of hell.