57 ms·

I agree with using Jupyter to get a good grasp of everything that’s going on and experimenting. However, while doing so, I think it’s good to keep in mind build

I agree with using Jupyter to get a good grasp of everything that’s going on and experimenting. However, while doing so, I think it’s good to keep in mind building something that’s not in a notebook format as I think notebooks tend to foster bad coding practices. This is from my experience as someone straddling both academia and a data science position in a startup where I have seen it rampant on both ends (slightly more understandable in academia but terrible for anything that actually goes into production).

ivansavz 3y ago
Yes, totally agree. I was thinking of notebooks strictly as the first contact... get the notion of python commands, variables, syntax, etc. It would be great to "move out" all the working code that has been REPL-tested into a separate file. Bonus points if it is a standalone command-line-runnable script that does something useful, e.g. after reading inputs from `sys.argv`. The exposure to running programs in the command line is probably a key skill I would include in the ABSOLUTE BEGINNER (because it is a prerequisite for so many other things). I suppose running a "server" would also be good to learn (even if just localhost), but that's getting into the HTTP/TCP/IP stack, so I would cover that CODING 102, not CODING 101.
- codinglearner 3y ago
  Thanks, this is really helpful! I did not know https://jupyter.org/ https://jupyter.org/ before!