<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Developer Tools on Farid</title><link>https://polymatx.dev/blog/tags/developer-tools/</link><description>Recent content in Developer Tools on Farid</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 04 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://polymatx.dev/blog/tags/developer-tools/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Parallel Coding Agents Need a Coordination Layer (So I Built Dibs)</title><link>https://polymatx.dev/blog/posts/dibs-coordination-for-parallel-coding-agents/</link><pubDate>Tue, 04 Aug 2026 00:00:00 +0000</pubDate><guid>https://polymatx.dev/blog/posts/dibs-coordination-for-parallel-coding-agents/</guid><description>&lt;p&gt;Running one AI coding agent is last year&amp;rsquo;s workflow. My normal setup today is two or three Claude Code sessions working the same repository from separate git worktrees — one refactoring, one writing tests, one chasing a bug. It is a genuine productivity multiplier, with one recurring failure mode:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Agent A is halfway through refactoring &lt;code&gt;src/auth&lt;/code&gt;. Agent B decides the quickest fix for its bug also lives in &lt;code&gt;src/auth/token.go&lt;/code&gt;. Neither knows about the other. The result is silent overwrites or an unmergeable diff — produced by two tools that were each doing their job correctly.&lt;/p&gt;</description></item></channel></rss>