You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: