<?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/ecf1e420ad4344a784cc071dc431429f&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/ecf1e420ad4344a784cc071dc431429f-29e69af046699396.gif</thumbnail_url><duration>1191.083</duration><title>Day 15 - Workset Grabber - 06 Stress Test</title><description>In this video, I walk you through our stress testing process for the code, ensuring it’s robust and user-friendly. We optimized our code down to 9 lines, focusing on handling scenarios like non-work shared models and user selection errors. I also explored AI assistance for code improvement, which led to some valuable insights about performance and naming conventions. I encourage you to review the changes and consider how you can apply these practices to your own projects. Happy coding!</description></oembed>