<?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/470d0788703541b2a5d843950ffc1409&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/470d0788703541b2a5d843950ffc1409-f04aeaaba2a65103.gif</thumbnail_url><duration>134.711</duration><title>Debugging Tips with MDX Playground 🛠️</title><description>In this video, I walk you through a frustrating debugging issue I encountered on line 209 of our code. I discovered that using the MDX Playground can simplify the process of identifying and fixing errors. I suggest we consider adding clearer instructions for troubleshooting in our documentation. Please take a look and let me know your thoughts on this approach!</description></oembed>