Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

From a chaotic EDA to an organized workflow #14

Open
robschick opened this issue Jan 16, 2019 · 0 comments
Open

From a chaotic EDA to an organized workflow #14

robschick opened this issue Jan 16, 2019 · 0 comments

Comments

@robschick
Copy link

Do you think you all can touch on how/when to ease the transition from, for me at least, what usually starts out as a pretty free-flowing and chaotic EDA on a new project, to the type of scripted and controlled workflow that was covered yesterday? My research projects tend to be pretty unstructured at first, and even though I use version control, can get a bit bloated as I try new analyses. If when we settle on a workflow like that covered yesterday, what do we do with all the other code? Keep it in a repository, and start a new, smaller and refactored one?

You mentioned it a bit with the smell-test.R file, but I often end up with an entire smell test repo. Should these all be on branches?

Cheers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant