4 ms·
Why shouldn't they use nbdev if it works for them? Plain Git obviously does not work and not only for data scientists. Git, with its inability to deal with non-
by tsss 3y ago
Why shouldn't they use nbdev if it works for them? Plain Git obviously does not work and not only for data scientists. Git, with its inability to deal with non-textual artifacts, is completely unsuited to a modern software development workflow. Modern software development contains interactive graphs, audio and video assets, editable diagrams, vast amounts of binary data for reproduction of experiments, etc. etc. So much custom tooling has been built to somehow shoehorn this stuff into git and it never works well. I'm sick of diagramming software and IaC tools with horrible user experience just to keep a plaintext representation that no human dares to read anyway.
- softwaredoug 3y agoI'm not against notebooks. I'm against the idea of doing all of your software development in notebooks. There's a sane way to use notebooks. For me, nbdev is a step too far, as it really pushes notebooks as the primary dev artifact. (All my opinions, people can do whatever they want)
- taeric 3y agoI am assuming you've seen this? https://www.youtube.com/watch?v=7jiPeIFXb6U https://www.youtube.com/watch?v=7jiPeIFXb6U :D
- softwaredoug 3y agoYes I'm a big fan :) I also like the "Why I like notebooks" counterpoint talk. I'm just not personally convinced. While they make some great arguments about where notebooks can be really powerful for software development, I don't think the speaker makes entirely valid counterpoints to the original "I don't like notebooks" talk and most of the problems of notebooks still stand. See this gist I posted above https://gist.github.com/softwaredoug/d527a18643f29832b0f41af309f9ab98 https://gist.github.com/softwaredoug/d527a18643f29832b0f41af...