<?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/c6edbd8d5269451d9f4ca3f6ca21f9d6&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/c6edbd8d5269451d9f4ca3f6ca21f9d6-6c7625230dc88c15.gif</thumbnail_url><duration>54.541667</duration><title>Day 16 - Crash-n-Clash - 00 Welcome</title><description>In today&apos;s lesson, I&apos;m excited to tackle the challenge of clashes on site that can derail our project timelines and budgets. We&apos;ll be creating a crash and clash tool that allows you to identify intersecting elements using custom rules, focusing on intersection filters and understanding element bounding boxes. I&apos;ll guide you through the process, including how to avoid common pitfalls. By the end, we&apos;ll produce an interactive output table to help us visualize our results. So, let&apos;s dive in and get started!</description></oembed>