<?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/62423be90b494eee845546d193820999&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/62423be90b494eee845546d193820999-a5fe31445f3d0a27.gif</thumbnail_url><duration>560.833333</duration><title>Day 01 - InPlace - 06 - Stress-Test</title><description>In this video, I walk you through the stress testing of our tool, emphasizing the importance of breaking it ourselves before anyone else does to maintain trust and reputation. I demonstrate how to handle potential errors, particularly with elements that lack types or families, and show how to improve user feedback when no elements are found. Additionally, I discuss the necessity of checking for any API changes that could affect our code. I encourage you to use tools like ChatGPT to analyze your code for potential issues efficiently. Please take note of these improvements and apply them as we prepare to ship the tool.</description></oembed>