Analytics work needs to be two things to scale well:
- Discoverable
- Reproducible
And [this'll be a bit controversial, but] to get there:
- Use SQL when possible (vs Py/R).
- Don't share work primarily through git.
Read more
, and fight me!
https://towardsdatascience.com/how-to-scale-your-analytics-org-by-ditching-git-3d8d4ce398d1 …
-
-
another possible way to think of this is methods-first (DS in this diagram) and business-context-first (analyst in this diagram). if your home base is the methods you learned in your academic training, it makes sense that you feel less fluent when you move to SQL
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Wow, I didn't have this experience so far!! I actually find SQL useful because it's really easy to pick up, so many users from different backgrounds/teams can understand it. I just find it hard sometimes to write concise clean code. And I tend to go to R/Python if I want to test.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.

