A notebook-free notebook or Jupyter dev env for coders
1–10 of 22 posts
Re: A notebook-free notebook or Jupyter dev env for coders
#2As long as this works for the author, good for them. What I found out looking at post after post, tool after tool, press release after press release, is that these tools optimize for the workflow of n=1 person working on a toy project with no stakes.
There is a disconnect:
- Most non-trivial machine learning projects I've seen involve more than one person and have stakes.
- Most people do not work on non-trivial machine learning projects with stakes
The map becomes the territory: many people then develop "ML project lifecycle management" or improve the "notebook experience" with better stylesheets for that kind of experience. i.e: the experience of one person working on a toy project for a YouTube video or a Medium blog post on "production machine learning" from someone who's never done it before.
I'm not pissing on those who produce this kind of content; they're likely doing it for feedback. I'm selfish in that it is part of my job to stay up to date but the low signal to noise ratio gives the feeling of being rickrolled with every piece of content about machine learning.
Re: A notebook-free notebook or Jupyter dev env for coders
#3Thanks for sharing your experience.
One minor critique: the vim stuff looks like a red herring given the topic. I'm personally not particularly interested in vim but am interested in jupyter notebook-alternative setups - I'd either remove it or explain why it's relevant here or contextualise it in some other way.
Re: A notebook-free notebook or Jupyter dev env for coders
#4Thanks for sharing your experience. One minor critique: the vim stuff looks like a red herring given the topic. I'm personally not particularly interested in vim but am interested in jupyter notebook-alternative setups - I'd either remove it or explain why it's relevant here or contextualise it in some other way.
It's relevant to him and his experience not to mention that of plenty of other developers. Why tell OP to remove it when you can just ignore it?
Re: A notebook-free notebook or Jupyter dev env for coders
#5As long as this works for the author, good for them. What I found out looking at post after post, tool after tool, press release after press release, is that these tools optimize for the workflow of n=1 person working on a toy project with no stakes. There is a disconnect: - Most non-trivial machine learning projects I've seen involve more than one person and have stakes. - Most people do not work on non-trivial mach…
Whenever I see a notebook, I think, "Where are the tests?"
Re: A notebook-free notebook or Jupyter dev env for coders
#6Thanks for sharing your experience. One minor critique: the vim stuff looks like a red herring given the topic. I'm personally not particularly interested in vim but am interested in jupyter notebook-alternative setups - I'd either remove it or explain why it's relevant here or contextualise it in some other way.
It's relevant to him and his experience not to mention that of plenty of other developers. Why tell OP to remove it when you can just ignore it?
Was clearly suggesting, not telling. And clarification was suggested also as an alternative.
In the context as described it's not obvious why it's relevant (especially to a non-vim user).
Constructive feedback was being offered, is all.
Re: A notebook-free notebook or Jupyter dev env for coders
#7I just want emacs shortcuts in my notebooks.
Edit: is there anyway of doing this? I am happy to compile a whole browser with custom shortcuts, if it's not too much work.
Re: A notebook-free notebook or Jupyter dev env for coders
#8For kicks, type in "import antigravity" in the VS Code Interactive tab and hit Shift-enter ;)
Re: A notebook-free notebook or Jupyter dev env for coders
#9I just want emacs shortcuts in my notebooks. Edit: is there anyway of doing this? I am happy to compile a whole browser with custom shortcuts, if it's not too much work.
You don't need to customise a browser. Just use emacs. Try writing "notebooks" in org-mode using emacs-jupyter.
https://orgmode.org/ https://github.com/nnicandro/emacs-jupyter
Re: A notebook-free notebook or Jupyter dev env for coders
#10As long as this works for the author, good for them. What I found out looking at post after post, tool after tool, press release after press release, is that these tools optimize for the workflow of n=1 person working on a toy project with no stakes. There is a disconnect: - Most non-trivial machine learning projects I've seen involve more than one person and have stakes. - Most people do not work on non-trivial mach…
Whenever I see a notebook, I think, "Where are the tests?"
Generally speaking, the tests were writing the code in the notebook and looking at the results. At least most of the stuff I use notebooks for is either one off or difficult to test. One off stuff might be some exploratory analysis or glue code to do simple tasks like loading and formatting data. Numerical tasks like ML are frequently very difficult to test because the author doesn’t know exactly what the output should be. If you don’t know the answer it’s hard to test for it.
For these reasons, formal tests rarely make sense in notebooks. If the code expands its use to being used repeatedly then clearly the notebook should be refactored into scripts and packages that have tests for the glue code and maybe some attempt at boundary the behavior of the numerical code.