> 4. The non-linear workflow of Jupyter This has always seemed crazy to me for something that is called a notebook and seems designed for exploratory analysis.

> 4. The non-linear workflow of Jupyter This has always seemed crazy to me for something that is called a notebook and seems designed for exploratory analysis. It seems like there should be a record of the order cells were run, and what their contents were when they were run, unless you have chosen "Kernel > Restart & Run All". Also, why isn't that command given prime importance with at least a button in the toolbar? I thought I was just using Jupyter wrong, so it is a little surprising to see the same complaint from someone who has used it "roughly 3 years up to 60% of my time". I like the model of using RStudio with KnitR. I rerun the entire document every now and then to make sure it accurately describes the thought process in a coherent narrative. I can cache results of operations that take a long time, but doing that is explicit, and the command to do so can be found in the code, rather than a consequence of an unrecorded action.