May we use cookies so Meta, Google, LinkedIn and ChatGPT see your visit and we learn which ads work? PrivacyMay we use cookies to see which pages help, and let Meta, Google, LinkedIn and ChatGPT see your visit, so we know which of our ads work? That way we spend less on ads that do not work. We do not sell your data, and the site works the same if you decline. You can change your answer at any time under Cookie settings at the foot of the page. Privacy policy
Loading...
This idea carries a full system design question on its own. Each walks through the full answer.
AI Engineering · Packaging And Registry
Free preview: the first 2 parts of this 26-part lesson.
Already bought the course? Sign in to read the whole lesson.
this lesson is part of
Generative AI and Agentic AI Engineering
Unlock this lesson and the 208 other paid lessons
$35 once, by card or PayPal
See the Generative AI and Agentic AI courseread the rest of this lesson in
Generative AI and Agentic AI Engineering
Unlock this lesson and the 208 other paid lessons
$35 once, by card or PayPal
See the Generative AI and Agentic AI coursein Packaging And Registry
This lesson is part of the AI Engineering course. Unlock the full course, a separate one-time payment, for lifetime access.
One-time payment by card or PayPal
Get Lifetime AccessOne-time payment: UPI, card or netbanking
Get Lifetime AccessFoundation lessons of this course are free, no payment needed. Try them now
Let me start with a long printed list of steps, like the one in the picture.
Imagine a workshop where a machine prints instructions for building something. Each step says exactly where to find a part: "take the small spring from drawer 14, shelf B". Another workshop, built the same way, can follow the list and build the same thing. But what if the second workshop is newer, and someone moved the small spring to drawer 15? The list still says drawer 14. The worker stops at that step, because the part is not where the list says.

Now imagine the opposite case. The list was printed in the new workshop, and an older workshop follows it. If every part it names is also in the old workshop, in the same place, the old one builds the same thing. Nobody would guess which direction is safer without trying both.
A saved machine learning model is a list like this. In this lesson I try both directions, for real, across four releases of one library over three years.
This lesson uses the model from the features chapter. If it is new to you, please read what a feature is first. That lesson built six features for each customer of a real online shop. It asked one question: at the start of a month, will this customer buy something in the next 30 days? The model is a gradient boosted tree model from scikit-learn, and it scored a test AP of 0.5450.
Three other lessons sit close to this one. The first lesson of this chapter opens a pickle file and shows what is inside. Here I only use one fact from it: a pickle file holds names of Python things, and loading it looks those names up. Saving formats compared saved the model eleven ways and loaded every file back, always with the same library versions on both sides. It ended by saying the cross-version question belongs to this lesson.
And lineage and rollback, in the lifecycle chapter, has a slide called "What I Did Not Measure: Library Versions". This lesson measures exactly that.