Why developers need statistics, or how to improve product quality
summary
Describes how Badoo uses technical metrics to give developers ownership of features: what metrics to collect, how to collect, store and visualize them, and how those statistics help detect technical issues and root causes to improve product quality. Covers concrete approaches and tooling used at Badoo for quickly finding and diagnosing technical problems.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:52Why developers need statistics
- 5:02Developer statistics types
- 10:40Anti-events importance
- 13:31Optimizing event storage
- 15:41Event delivery and processing
- 17:05Raw vs aggregated storage
- 19:18Metrics and uniqueness calculation
- 20:44Statistics visualization
- 23:35Anomaly detection
- 28:06Handling anomalies
- 31:17Real-world stats workflow
- 37:00Q&A: Justifying dev time
- 37:47Q&A: What to log
- 39:10Q&A: External events vs issues
- 46:42Q&A: Nighttime monitoring
related talks
26mMetrics and Modeling – Helping Teams See How to Improve
40mBuilding Data Cultures
46mUsing Analytics to Improve Quality
28mProduct metrics for developers
24mMetrics-driven development
39mReliable analytics: how we collect stats in VK mini-apps
34mTen Tips to Leverage Data Better and Make Better Products
23mUsing Data to Bridge Product and Engineering Teams