Re:Why Jupyter is data scientists’ computational notebook of...
by LeanderK on Tuesday October 30, 2018 @10:10AM
(#18336580)
diving code between models/data-pipelines and experiments. Notebook are used for visualization and telling a story why you tried what for the other team-members.
[ Parent
| on HN ]
Re:Why Jupyter is data scientists’ computational notebook of...
by agibsonccc on Tuesday October 30, 2018 @10:22AM
(#18336693)
Yeah but the whole point is "interactive coding". It doesn't feel very interactive when I have to context switch all the time :). I'd prefer something closer to what the lisp folks get to do with the repl where you can scratch out an idea and see it working without leaving your environment.
Re:Why Jupyter is data scientists’ computational notebook of...
by LeanderK on Wednesday October 31, 2018 @08:37AM
(#18345127)
well, I don't think so. Not everything you do is interactive. Data exploration and basic model selection is, but complex models and more complicated data-pipelines/preprocessing isn't, I think.
Tensorflow is the opposite of interactive, even in a notebook.
putting models (in a sense of more complicated models, not just a SVM), data-pipelines, shared visualization-code in a src folders and experimenting in the notebook divides stuff that's interactive by nature from "real" coding. I don't context-switch that much to be honest.
I don't really copy code into cells, because I only experiment there.
Also, what happens if you need to share code between notebooks?
I think notebooks should be simple and explain the experiments and the reasoning behind them to your coworkers. Otherise it's hard to coordinate and learn from each others insights into the data.