<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Developer Tooling on Derick Chen</title><link>http://www.buildwithdc.co/tags/developer-tooling/</link><description>Recent content in Developer Tooling on Derick Chen</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 03 Jul 2026 10:00:00 +0800</lastBuildDate><atom:link href="http://www.buildwithdc.co/tags/developer-tooling/index.xml" rel="self" type="application/rss+xml"/><item><title>Beyond AI-Driven Development, Part 1: Tooling - The AI as the New Compiler</title><link>http://www.buildwithdc.co/posts/beyond-ai-driven-development-part-1-the-ai-as-the-new-compiler/</link><pubDate>Fri, 03 Jul 2026 10:00:00 +0800</pubDate><guid>http://www.buildwithdc.co/posts/beyond-ai-driven-development-part-1-the-ai-as-the-new-compiler/</guid><description>If your tooling still optimizes for typing speed, you&amp;rsquo;re optimizing a solved problem.
I keep sitting down with engineering leaders who ask the same question in different words: &amp;ldquo;We&amp;rsquo;ve adopted AI coding assistants. Productivity is up. So why does everything still feel like it&amp;rsquo;s running on 2015 infrastructure?&amp;rdquo;
Here&amp;rsquo;s the answer nobody wants to hear: your tools were never the bottleneck you thought they were. They were built to solve a problem AI has already solved.</description></item></channel></rss>