Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Future of Notebooks: Lessons from JupyterCon

willcrichton.net

Post reply on HN
Print view View original

101–110 of 158 posts

Re: The Future of Notebooks: Lessons from JupyterCon

#101

Post by d0mine »

chimprich wrote: post #72
dangirsh wrote: post #42

Earlier quoted context omitted.

ob-ipython enables IDE-like editing features within the code cells. It's embedded in a polyglot, git-friendly, literate programming environment called Org-mode. I use it every day and love it. Other goodies: - easily manage multiple kernels (in different languages / machines) in one file - tree-based organization manages complexity better than linear notebooks - no browser in sight (unless you need interactive widget…

Interesting. I use emacs for hacking Python but I've never heard of this tool. Do you actually use this for software development or is it more of a data-science-type exploration tool?

related "literate devops in emacs" https://youtu.be/dljNabciEGg

Re: The Future of Notebooks: Lessons from JupyterCon

#102

Post by superdaniel »

stevesimmons wrote: post #38

I don't get the people here saying don't use Jupyter notebooks, or they are bad software engineering. So much Python development is trying snippets of code in a REPL as you introspect live objects, then once they're right pasting them into the IDE. All my Jupyter notebooks are like that, where my code starts as cells of a line or two, as I check each output. Then I coalesce them into a function (which avoid the probl…

I just wish it wasn’t so tedious to version control Jupyter notebooks. I always try and clear the output before I stage it so I don’t have large binaries of plots or figures that were generated.

Re: The Future of Notebooks: Lessons from JupyterCon

#103

Post by dangjc »

I can’t recommend enough using Atom with the Hydrogen plugin. A Jupyter kernel runs in the back and you can execute a line or multiple lines of code at once just like the web notebooks. But you’re editing a plain code file, not an .ipynb, which is easy to check into git, move to inside a library, and get full IDE tooling on.

Re: The Future of Notebooks: Lessons from JupyterCon

#104

Post by billfruit »

jakelarkin wrote: post #3

I understand why they became popular, but as a software engineer considering how they work, I am just full of disappointment. we're going to spend the next ten years re-inventing every single software engineering best practice for jupyter's weirdo environment.

People are already doing bad programming practices in large scale with MATLAB, I guess jupyter is a step up from that.

Re: The Future of Notebooks: Lessons from JupyterCon

#105

Post by mi_lk »

mi_lk wrote: post #88
stevesimmons wrote: post #38

I don't get the people here saying don't use Jupyter notebooks, or they are bad software engineering. So much Python development is trying snippets of code in a REPL as you introspect live objects, then once they're right pasting them into the IDE. All my Jupyter notebooks are like that, where my code starts as cells of a line or two, as I check each output. Then I coalesce them into a function (which avoid the probl…

> Over time, I expect editors like VSCode to edit Jupyter notebooks natively. Please, please, please. Given the rising importance of interactive programming, I really think it deserves more than a extension to give us a seamless experience.

Related issue: https://github.com/Microsoft/vscode/issues/34739

Re: The Future of Notebooks: Lessons from JupyterCon

#106

Post by dec0dedab0de »

michaelmrose wrote: post #33
dec0dedab0de wrote: post #22

Earlier quoted context omitted.

Jupyter is also really useful for figuring out how you want to do something before you copy it to your IDE. Every time I work with a new API or library I try it out in jupyter first.

What are the benefits of this vs just an integrated repl?

Being able to re-run and modify cells out of order.

Re: The Future of Notebooks: Lessons from JupyterCon

#108

Post by LrnByTeach »

pacala wrote: post #92
stevesimmons wrote: post #38

I don't get the people here saying don't use Jupyter notebooks, or they are bad software engineering. So much Python development is trying snippets of code in a REPL as you introspect live objects, then once they're right pasting them into the IDE. All my Jupyter notebooks are like that, where my code starts as cells of a line or two, as I check each output. Then I coalesce them into a function (which avoid the probl…

Jupyter code is draft code. Draft code rarely makes into clean code, because it requires extra tedious effort. Most of us are too overworked to have the time or energy to perform it. Alternatively one can write exploratory code as unit tests and run them inside an IDE. When the exploration is done, three quarters of the tedious cleanup effort is already done. There are already unit tests. There are already APIs exerc…

This is how I code, exploratory code as unit tests ....

> Alternatively one can write exploratory code as unit tests and run them inside an IDE. When the exploration is done, three quarters of the tedious cleanup effort is already done. There are already unit tests. There are already APIs exercised by the unit tests. The code is in much better shape.

Re: The Future of Notebooks: Lessons from JupyterCon

#109

Post by cirgue »

rmetzler wrote: post #84
jorgemf wrote: post #52

Earlier quoted context omitted.

Jupyter notebooks are for data science, mostly because visualization is required. Something you do once, report it and it is done. Itsn't make sense to use Jupyter for other stuff. It doesn't make much sense to use them for training big models of deep learning because there are better tools for that.

What tools can you recommend for machine learning?

Scripts to train the model, Jupiter to do your analysis. This is, AFIK, what most ML shops do if they’re using python.

Re: The Future of Notebooks: Lessons from JupyterCon

#110

Post by dfee »

stevesimmons wrote: post #38

I don't get the people here saying don't use Jupyter notebooks, or they are bad software engineering. So much Python development is trying snippets of code in a REPL as you introspect live objects, then once they're right pasting them into the IDE. All my Jupyter notebooks are like that, where my code starts as cells of a line or two, as I check each output. Then I coalesce them into a function (which avoid the probl…

Honestly, I just use a file called `play.py`, create a function called `test_it()` or something, and maybe use ipdb if I need to stop somewhere and explore.

Then: `pytest -s play.py`

I just don’t understand what the appeal of Jupyter is, but iPython is great.

Post reply on HN