What Data Analysts Wish Application Developers Knew
summary
Concrete recommendations and failure cases: missing intermediate snapshots prevents save distinctions for reconciliation so demo and trial metrics diverge; inaccessible logs force building parsers; lacking history breaks FIFO accounting (50 shirts then 30 stickers); missing UTM/foreign keys prevents funnel attribution; silent schema changes cause wrong reports (50 vs 500 new customers) or bad invoices ($500,000 becomes $5,000). Fixes are specific: audit table for money, store external system keys, small tools (a Flask mapper), release tags and tests plus rollbacks and communication.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:47Developer-analyst concepts
- 3:34Mismatched metrics
- 7:27Missing ticket data
- 8:53Silent schema changes
- 12:09Inventory audit gaps
- 14:37Disconnected funnel data
- 17:28Invoice bugs and fixes
- 19:59Key takeaways
- 21:00Curiosity in collaboration
- 21:20Q&A
related talks
40mBuilding Data Cultures
52mScaling Data Teams: Three Pitfalls and How To Avoid Them
35mBad data - anecdotes and examples from the real world
01h 05mKEYNOTE: Why Customers Can’t or Won’t Use Your Technically-Right Data Products
38mData Secrets from a Platform Engineer
37mPitfalls and pro-tips for effective and transparent BI tools data science & applications
40mThe Hidden Cost of Data Debt
37mEngineering data quality