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 24-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.
Imagine a library where the librarian has read every book. She does not shelve the books by their number. She puts books that feel alike next to each other: cookery here, birds there, old maps in the corner. When you ask for something, she points at a shelf, not at one book.
Now suppose she wants to guess which readers will come back next month. She could look at how often each reader came, and how recently. Or she could look at which shelves each reader took books from. The shelves sound richer. They say something about taste. But will they help her guess who comes back? Taste and loyalty are not the same thing.

This lesson asks the same question about a real shop. Every product has a name. A computer can place names that mean similar things close together, like the librarian's shelves. I measure whether that helps a model guess which customers will buy again.
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. It also built six simple facts about each customer, which I reuse here as the starting point. They are how recently they bought, how often, and how much they spent. The other three are how much they sent back, how long they have been a customer, and how many different products they bought.
Lesson 7, on categorical features at scale, gave the model the product CODES a customer bought. A code like 85123A is only a label. It says nothing about the product. The best result there came from filing codes into numbered drawers, and the gain was tiny.
This lesson gives the model the product NAMES instead, turned into numbers that carry meaning. If meaning matters, this is where it should show.
What an is, and how two of them are compared, is taught in the tokens and embeddings chapter: what an embedding is and cosine, dot and distance. I do not teach it again here. I only use it.