Data Science at the Command Line
datascienceatthecommandline.com
Data Science at the Command Line
1–10 of 36 posts
Re: Data Science at the Command Line
#2Re: Data Science at the Command Line
#3All this attention (read: likes, shares, and page views) is making me wonder whether it's worthwhile to write an update (or even a second edition). What do you think? What would you like to see changed or added?
Re: Data Science at the Command Line
#4Re: Data Science at the Command Line
#5While the efficiency of a command line is always sexy, but for data science in particular , where reproducibility is important and bugs are subtle and often don't cause a terminal error, it is worth it to sacrifice a little bit of code efficiency for code clarity in the long run by using an IDE/Notebook.
Re: Data Science at the Command Line
#6While the efficiency of a command line is always sexy, but for data science in particular , where reproducibility is important and bugs are subtle and often don't cause a terminal error, it is worth it to sacrifice a little bit of code efficiency for code clarity in the long run by using an IDE/Notebook.
Is there a tool that would create a notebook from the command-line?
Re: Data Science at the Command Line
#7While the efficiency of a command line is always sexy, but for data science in particular , where reproducibility is important and bugs are subtle and often don't cause a terminal error, it is worth it to sacrifice a little bit of code efficiency for code clarity in the long run by using an IDE/Notebook.
Is there a tool that would create a notebook from the command-line?
[0]: https://blog.dominodatalab.com/lesser-known-ways-of-using-no...
Re: Data Science at the Command Line
#8Earlier quoted context omitted.
Is there a tool that would create a notebook from the command-line?
Jupyter notebook has Bash kernels
Re: Data Science at the Command Line
#9While the efficiency of a command line is always sexy, but for data science in particular , where reproducibility is important and bugs are subtle and often don't cause a terminal error, it is worth it to sacrifice a little bit of code efficiency for code clarity in the long run by using an IDE/Notebook.
At best you’re constantly restarting your kernel and clearing output. More likely, output from cell #7 has modified output [138] but you haven’t updated the chart produced in cell #17 (or some similar craziness). Not much better than programming with GOTOs.
“But they’re great for reporting and visualization!” you might say. If you’re building any report of value, though, it will influence important decisions. That’s the reason your code shouldn't live in a notebook. It should be in a library, covered by unit tests, so that those decisions aren’t based on faulty logic.