Honest Take — Before You Begin
This is your module. This is where years of Rails engineering stop being irrelevant to ML and become your biggest advantage.
ML Systems, Production, and Engineering covers: Designing Machine Learning Systems, Introducing MLOps, The ML Solutions Architect Handbook, Fundamentals of Data Engineering. Bridge the gap between "I can train a model in a notebook" and "I can design, deploy, and maintain ML systems in production." This is where your years of Rails engineering experience become a superpower. This is the ML equivalent of your SRE/observability knowledge. Chip Huyen's book is like your "Designing Data-Intensive Applications" but for ML. The concerns are identical to what you know from Rails production: how do you deploy safely, how do you monitor for regressions, how do you handle schema changes (data drift), how do you roll back a bad deploy (model rollback). Different vocabulary, same engineering discipline.
This course unlocks once you've finished its prerequisite. Open prerequisite →
This is your module. This is where years of Rails engineering stop being irrelevant to ML and become your biggest advantage.
Somewhere right now, a model that scored beautifully in a notebook is quietly making worse and worse predictions in production, and nobody has noticed yet. No exception was raised…
Here is a question the previous book's diagrams cannot answer: the retrained churn model looks better on last month's data — who decides it goes live? The data scientist who train…
At some point in the next few years, someone senior will turn to you in a meeting and ask: "Should we fine-tune our own model, use an API, or not do this at all — and what will ea…
You know databases. Years of Postgres, indexes you can reason about, migrations you trust, N+1s you can smell through a closed door. Here is the uncomfortable news: in the ML worl…
Work through each item before the checkpoint.
Design an ML system architecture on paper: data pipeline, feature store, model training, serving, monitoring, retraining triggers. Explain every component and why it exists.
7 lessons. Read in order; spiral back when you need to. By the end you'll have used the core ideas twice — once on the abstract, once on something you'll meet at work next week.