Review how Airbnb or Netflix solved a recommendation or ranking problem before building your own system.
Find documented failures and lessons learned from major companies to avoid repeating their mistakes.
Understand the full ML lifecycle from data engineering through model deployment by reading case studies across 30+ topic areas.
Learn what validation, A/B testing, and privacy techniques companies actually use in production rather than in theory.
applied-ml is a curated reading list of papers, technical blog posts, and articles published by companies describing how they use machine learning and data science in real production systems. Rather than academic research, the focus is on practical, deployed applications, what problem was framed, which techniques were tried, why certain approaches worked, and what measurable results were achieved. The list is organized into over 30 topic areas covering the full lifecycle of a machine learning system. Topics include data quality and engineering, feature stores (centralized repositories for the input data fed to models), search and ranking systems, recommendation engines, natural language processing, computer vision, anomaly detection, forecasting, embeddings (a technique for representing data as numerical vectors), reinforcement learning, model management, and the human practices and team structures behind ML teams. There are also sections on validation and A/B testing, privacy-preserving techniques, and documented failures. The contributing companies include names like Airbnb, Uber, Netflix, Google, Meta, LinkedIn, Pinterest, Shopify, DoorDash, Lyft, and many others. A data scientist or machine learning engineer who is designing a system and wants to learn from how comparable organizations approached the same type of problem, before committing to an architecture, would use this list as a reference. It answers the question "how did others actually do this in production?" rather than "what does the theory say?".
Generated 2026-05-18 · Model: sonnet-4-6 · Verify against the repo before relying on details.