Data Modelling is not a one man job!
summary
Argues that data modelling must be collaborative and automated, showing how WhereScape 3D plus GIT pipelines let multiple designers share models, enforce code standards, run data tests and deploy to a physical platform. Gives concrete failure example where a bank’s load used 3x data volume and crashed nightly loads, cites missing business rules and tooling limits as common causes, and says automated CI/CD from design to deploy prevents those missteps.
AI-written summary · about
chapters (11)
- 0:00Data modeling introduction
- 3:40One-person modeling challenges
- 6:07Collaborative requirements gathering
- 8:35Involving data engineers
- 10:22Modeling pitfalls in SDLC
- 12:50Team dynamics and skills gaps
- 14:56Tooling limitations
- 17:47Effective modeling tools
- 19:13Departmental alignment
- 20:14Automated deployment
- 20:56Q&A
related talks
39mPanel Discussion
30mDATA MODELLING IS DEAD! LONG LIVE DATA MODELLING!
26mDataEngBytes 2023 - MEL-T1-01 - Joe Reis
24mMake data central feature
26mData, It’s a People Problem: Understanding the Sociotechnical Elements of a Data-Driven Organization
27mDataEngBytes 2023 - BRI-T1-07 - Joe Reis
43mData Modelling for Startups: Domain Models & the Modern Data Stack
31mExecuting An Effective Data Strategy: Why Automation Is No Longer A Choice
