Hi, Hamel here. I'm one of the co-authors. I'm an independent consultant and not all clients allow me to talk about their work.
However, I have two that do, which I've discussed in the article. These are two production use cases that I have supported (which again, are explicitly mentioned in the article):
Eugene Yan works with LLMs extensively at Amazon and uses that to inform his writing: https://eugeneyan.com/writing/ (However he isn't allowed to share specifics about Amazon)
We were working on this webpage to collect the entire three part article in one place (the third part isn't published yet). We didn't expect anyone to notice the site! Either way, part 3 should be out in a week or so.
Hello this is Hamel, one of the authors (among the list of other amazing authors). Happy to answer any questions as well as tag any of my colleagues to answer any questions!
(Note: this is only Part 1 of 3 of a series that has already been written and the other 2 parts will be released shortly)
Hi Jeremy, Hamel here. I submitted this blog post, and definitely did not submit it in this form. One of the defining features of this blog post was the F word.
Excellent comment and question. Re: commercializing nbdev, this path didn't seem to make sense to me personally (for reasons I outlined), but they very well could make sense for others.
But I'm with you, I really like many of the ideas presented in nbdev and feel like they have legs. I don't think those ideas should be abandoned or thrown away. Posit (https://posit.co) is developing products that draw from many of the ideas in nbdev - infact we are working with them - and I think the directions they are pursuing are very promising.
However, if you have ideas on how to make tools in the space that draw on these ideas, I encourage you to do so. I will even support you to the best of my ability if you decide to.
No snark interpreted at all. Yes I am well aware of org mode and love it! I think it is fantastic. There are some key differences that I think make notebooks a bit more interesting - however it sounds like you've made a system you are happy with? I would love to see what you have! Mind sharing it?
I think a notebook is VERY different than an ephemeral REPL. I think that is worth considering when thinking about generating docs, tests and source code from a single source of truth (as opposed to separate files).
Yes, nbdev is a system that "compiles" notebooks to python scripts, tests and documentation all from one source of truth. Jupytext cannot do this (nor was it designed to)