<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/459b097f6790479291dd7f6cdc1932a8&quot; frameborder=&quot;0&quot; width=&quot;1470&quot; height=&quot;1102&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1102</height><width>1470</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1102</thumbnail_height><thumbnail_width>1470</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/459b097f6790479291dd7f6cdc1932a8-c1627fe8cdd97e96.gif</thumbnail_url><duration>518.202</duration><title>Jeffrey PartSelect Walkthrough</title><description>This Loom presents Jeffrey’s walkthrough of his PartSelect case study, focusing on how to frame the problem and design a code-based architecture for part discovery when customers only know something is broken. He explains that PartSelect has a huge catalog, but keyword search fails in these situations because most customers do not know what parts they need. The walkthrough includes demo cases and discusses key design decisions and their tradeoffs.</description></oembed>