The 10 commandments of reliable data science
summary
Ten concrete rules: start projects with a repeatable layout (example: cookiecutter-data-science), keep raw extracts immutable, run the DAG from raw input to final artifacts automatically, and centralize all model and run parameters. Use notebooks for exploration and move reusable code into source files so it can be unit tested; add assertion tests and logging so runs fail loudly and produce saved artifacts. Practical tools mentioned include NB Auto export, Makefiles and orchestration to reproduce results.
AI-written summary · about
chapters (11)
- 0:00Reliable data science intro
- 1:30Criticism of data science
- 4:43Organize projects early
- 7:53Version control for DS
- 10:01Notebooks for exploration
- 12:08Test assumptions
- 16:24Automate project runs
- 19:50Centralize parameters
- 21:54Log run artifacts
- 25:46Simplest end-to-end pipeline
- 28:14Q&A
related talks
26mThe Software Engineering Part of Data Science
31mWhy Most Data Projects Fail and How to Avoid It
20mWhy data privacy is critical for robust data management?
20mSkrub DataOps, Probabl
48mBecoming a Data Head, a reflection on the trade offs and decision
42mThe 7 habits of data effective companies
30mDevOps For Data Teams
32mWhy Most Data Projects Fail and How to Avoid It
