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...
AI Engineering · Features And Feature Stores
Free preview: the first 2 parts of this 28-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 newspaper.
An editor has a story that is too long for its page. Every paragraph takes space, and space costs money. So she cuts. She does not cut at random. She reads the story, finds the paragraph whose loss hurts the story least, cuts it, and reads again. Then she repeats, until the story fits.

Now imagine two paragraphs that say almost the same thing. If she asks "can I lose this one?", the answer is yes, because the other one still tells the reader. If she asks the same about the second one, the answer is also yes, for the same reason. Each paragraph looks useless. But if she cuts both, the story has a hole in it.
A machine learning model has the same problem with its inputs. Every input costs something to compute and to store, every day the model runs. Some inputs carry the story. Some repeat each other. In this lesson I measure which ones earn their place, on real data from a real shop.
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. That lesson built six simple features from each customer's history, such as how many days since their last order and how much they have spent. The question is always the same: at the start of a month, will this customer buy something in the next 30 days?
The lesson on window aggregations added 15 more columns: orders, spend and products over the last 7, 30, 90, 180 and 365 days. Together with the six, the model scored a little higher. But that lesson also noted that it now had more than three times as many columns.
The lesson on categorical features at scale added a block of 842 hashed columns for each customer's favourite product, for a small gain.
So I now have a pile of features, and each one has a price. This lesson asks the question a team asks once the pile gets big: which of these features earn their compute?