<?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/8f6b415cdac046aa8f1ef0b8a5a237e4&quot; frameborder=&quot;0&quot; width=&quot;1742&quot; height=&quot;1306&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1306</height><width>1742</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1306</thumbnail_height><thumbnail_width>1742</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/8f6b415cdac046aa8f1ef0b8a5a237e4-612c4c52c0941be2.gif</thumbnail_url><duration>144.98</duration><title>Managing Code Conflicts in Parallel Development 🚧</title><description>In this video, I discuss the challenges we faced with conflicting code changes from multiple AI coding agents working on the same repository. Agent Bob&apos;s recent pull request, while clean and passing CI, encountered 22 breaking conflicts with other branches, particularly due to changes in the &apos;create order&apos; function requiring three arguments instead of two. I&apos;ve highlighted specific lines in the code where these issues arise, including cross-language conflicts in Python and Ruby. It&apos;s crucial that we address these conflicts before merging to avoid crashes in production. Please review the highlighted lines and ensure your branches are aligned with the updated function signatures.</description></oembed>