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 · Features And Feature Stores
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 Features And Feature Stores
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 small picture from a shop.
Two people work in the same small shop. At the end of each day, the first one takes the pile of paper receipts and adds them up with a pen. The second one keeps a number on her phone, and every time a sale happens she adds it at once. Both are careful. Both follow the same instruction: "keep the total of today's sales".

Will their totals agree at closing time? Usually, yes. But think about the small questions the instruction does not answer. Does a sale made at exactly closing time count today or tomorrow? Is "today" judged by the shop's clock or by the bank's clock in another country? When a customer brings something back, do you subtract it from the total or leave it out? Each person can answer those questions in a sensible way, and still get a different number from the other.
Nobody made a mistake. They simply made different, reasonable choices.
Machine learning teams have exactly this situation, every day. In this lesson I build the two people in code, give them the same instruction, and measure how often they disagree and whether it matters.
This lesson uses the same shop, the same customers and the same question as the rest of the chapter. If any of that is new, please read what a feature is first. It sets up the data and the task, and it built six simple features that I use again here: recency, frequency, money, return share, tenure and products.
An earlier lesson, train/serve skew, already showed what happens when the input at serving time is simply wrong. Its examples were temperatures in Fahrenheit instead of Celsius, and every hour shifted by five. Those were broken inputs, and they did a lot of damage.
This lesson asks a harder and more common question. What if neither side is broken? What if both pieces of code are correct readings of the same definition, written by careful people, and they still disagree in small ways? Is that harmless, or does it quietly cost something?
The lesson on point-in-time joins made sure no feature sees the future. Every feature here, on both sides, uses only events before the cutoff, and the code checks it.