Some great perspectives from JupyterCon: reproducible/explicit state is important, notebooks are replacing bash scripts in some workflows, and they're even used to introduce programming to total beginners!
miniblog.
Related Posts
The lisp model of programming is generally: write a function, evaluate it, interactively call it with some arguments, iterate. Jupyter notebooks are similar.
Why not automatically evaluate definitions (not expressions) whilst working? It seems like it could be a satisfying way to work with code.
Reactive notebooks: cell state is immutable, unordered (unlike Jupyter) and naturally lends itself to interactive web UIs!
I Don't Like Notebooks: https://docs.google.com/presentation/d/1n2RlMdmv1p25Xy5thJUhkKGvjtV-dkAIsUXP-AL4ffI/preview?slide=id.g362da58057_0_1
A good discussion of the limitations of Jupyter. It's a challenging design space: you want a helpful code sandbox without reinventing the IDE.