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

Discuss cases in which workflow might break down #15

Open
angela-li opened this issue Feb 1, 2018 · 0 comments
Open

Discuss cases in which workflow might break down #15

angela-li opened this issue Feb 1, 2018 · 0 comments
Labels
workflow project oriented workflow

Comments

@angela-li
Copy link

A few folks mentioned that their companies have proprietary databases that they use to pull data, so they can't separate their data pull & analysis sections into multiple scripts. For example, there are instances where a company wouldn't suggest creating intermediate data, and certainly not to save it anywhere.

Maybe including a slide or two on when it would be a bad idea to write many small units for tidy analysis (or a disclaimer on one slide) would be helpful?

@edavidaja edavidaja added the workflow project oriented workflow label Jun 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
workflow project oriented workflow
Projects
None yet
Development

No branches or pull requests

2 participants