<?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/f655ba3401aa435f818a630febfc9c0a&quot; frameborder=&quot;0&quot; width=&quot;1386&quot; height=&quot;1039&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1039</height><width>1386</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1039</thumbnail_height><thumbnail_width>1386</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/f655ba3401aa435f818a630febfc9c0a-4581e6a940a8601b.gif</thumbnail_url><duration>167.536</duration><title>How I Loom: Engineering Leader</title><description>In this Loom, I share three key use cases for how I integrate Loom into my day-to-day work at Atlassian. First, I use it for Architectural Reviews to provide context behind design diagrams, enhancing feedback quality. Second, during Code Reviews, I explain my thought process for each line of code, which streamlines the review process and generates PR descriptions efficiently. Lastly, I utilize Loom for RFC documents to clarify my reasoning and foster better engagement and feedback. I encourage you to consider how these practices might enhance your own workflows.</description></oembed>