<?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/cec82fa42203448cb8a01763628f6acf&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/cec82fa42203448cb8a01763628f6acf-2a1cb88c560da512.gif</thumbnail_url><duration>1821.583</duration><title>Day 17 - SharedParam Smuggler - 6-StressTest</title><description>In this video, I walk through the stress test for our shared parameter smuggler tool, identifying and fixing potential issues in the code. I emphasize the importance of user checks and error handling, ensuring that we provide clear alerts when parameters are not selected. I also discuss the need for better organization in our functions and the potential use of AI for further improvements. Please review the updated code and the HTML report generated to see the enhancements made. I hope this tool will save you and your team valuable time.</description></oembed>