hello what are your strategies for keeping your code organized? I'm specifically struggling with more of the day-to-day small bits of code vs more "formal" functions & pipelines I've written (where it makes sense to use git). #phdchat
-
Show this thread
-
Replying to @MaureenBug
I generally do something like, / /bin /code /code/pkg1 /code/pkg2 /common_scripts /data /data/raw /data/intermediate /data/clean /notebooks /notebooks/01_Intro/001_Title.ipynb /notebooks/06_Conclusion/001_Title.ipynb
1 reply 0 retweets 2 likes -
Replying to @generativist @MaureenBug
Stuff I'll rerun (preferably via `make`) go in the bin directory. As far and as quickly as possible, I put my notebook code in proper unit-tested packages. Common scripts are stuff I include in Jupyter kernels and is mostly presentational / env setup stuff.
1 reply 0 retweets 1 like
Data partitioning is really useful for me, especially with pipelining. Things slowly bubble up to the clean directory. And, all my notebooks are in lexicographically sorted directories and file names so it's easy to compile later, but also: Namespaces are good!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.