Making Data Is Not the Same as Making Software — Or Is It?
summary
Compares building software with building data products, questioning whether software engineering practices apply unchanged when the product is data. Argues that code and data are different but not as much as they seem, and shows how long-standing best practices from other industries (some dating back 40 years) are becoming relevant again for data projects.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:06What is a data company
- 3:14First steps and digitization
- 4:39Initial focus and common mistakes
- 6:24Scaling data production
- 8:56Cultural clashes in teams
- 11:23Data engineering best practices
- 14:08Communication and vocabulary issues
- 16:18Automation and human factor
- 17:24Origin of DataOps
- 20:33Theory of constraints applied
- 21:20Understanding customer needs
- 22:58Solving taxonomy problems
- 24:27Automation: where to start
related talks
42mwhy software development is an engineering discipline
41mCan Data & ML really learn from software engineering?
18mIs It True We Do Development in Data?
42mwhy software development is an engineering discipline
47mKeynote - The Evolving Role of Data in Software Development
25mUnpacking The Data Product Experience So Far
42mBringing Software Engineering Rigour to Data, DataEngBytes 2022
47mData Quality vs Everyone
