<?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/da2d0c845a804761a68195d40f52d4fb&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/da2d0c845a804761a68195d40f52d4fb-0fe39947c25b52a6.gif</thumbnail_url><duration>514.917</duration><title>Day 09 - Auto-Planner - 07 StressTest</title><description>In today&apos;s video, I walked through the stress testing of our code to identify potential breakpoints before deployment. I emphasized the importance of checking for API changes, particularly regarding element IDs, and ensuring that we handle cases where there are no available apartments or rooms. I also discussed the need to verify that rooms are placed correctly to avoid unexpected behavior. I encourage you all to review the code and consider the suggestions I provided, especially around using try-except statements for better error handling. Let&apos;s make sure everything is bulletproof before we ship it out!</description></oembed>