Create the Data Scientist learning path

quaid commented 3 years ago

This involves creating a curriculum for Data Scientists from the existing materials; identifying any gaps where there is no material for a corresponding step in the path to know what material to create; and creating a curriculum page or area for this content on the website, as per the layout for the learning path part of the website.

quaid commented 3 years ago

@durandom Who knows this material—what exists, what might be needed, etc. toward creating this web page.

oindrillac commented 3 years ago

@quaid this is something I'm willing to support with and fill in the gaps for.

MichaelClifford commented 3 years ago

@quaid there is a fair amount of existing content we've created around data science projects. Is there a more specific scope/definition for the "data science curriculum" we are looking to provide here? That could help to guide us on identifying the existing content and potential gaps.

and thanks for volunteering @oindrillac :smiley:

quaid commented 3 years ago

Different from SRE where people are learning principles from scratch, the Data Scientist path here I think is all about:

Quickstart for every data science tool we host (written, video tutorial)
Useful ways to blend tools
Anything related to, if they have code that can be run in production, how can they gain benefits from Operate First open community cloud.
- E.g. what workloads can they start up, what colleagues can they attract

Consider what a Data Scientist working at a corporation might want to play around and learn from/with, show them how to open the toolbox/toybox, and go get productively lost.

So unlike SRE principles & practices, we aren't teaching data science, we're giving access to the latest and greatest open source data science tools for people to do things. Curriculum I think can focus on just that.

And maybe that means we can pull this page together most easily, so it is useful and demonstratea the learning path idea.

quaid commented 3 years ago

/label kind/website

sesheta commented 3 years ago

@quaid: The label(s) /label kind/website cannot be applied. These labels are supported: community/discussion, community/group-programming, community/maintenance, community/question, deployment_name/ocp4-stage, deployment_name/ocp4-test, deployment_name/zero-prod, hacktoberfest, hacktoberfest-accepted, kind/cleanup, kind/demo, kind/deprecation, kind/documentation, kind/question, sig/advisor, sig/build, sig/cyborgs, sig/devops, sig/documentation, sig/indicators, sig/investigator, sig/knowledge-graph, sig/slo, sig/solvers, thoth/group-programming, thoth/human-intervention-required, thoth/potential-observation, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, triage/accepted, triage/duplicate, triage/needs-information, triage/not-reproducible, triage/unresolved

In response to [this](https://github.com/operate-first/community/issues/51#issuecomment-882892792): >/label kind/website Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

quaid commented 3 years ago

This issue is related to https://github.com/operate-first/operate-first.github.io/issues/265

sesheta commented 2 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.