<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Guides on Derick Chen</title><link>http://www.buildwithdc.co/guides/</link><description>Recent content in Guides on Derick Chen</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 10 Jun 2026 12:00:00 +0800</lastBuildDate><atom:link href="http://www.buildwithdc.co/guides/index.xml" rel="self" type="application/rss+xml"/><item><title>The Human Side of AI Transformation: A Complete Guide</title><link>http://www.buildwithdc.co/guides/human-side-of-ai-transformation-guide/</link><pubDate>Wed, 10 Jun 2026 12:00:00 +0800</pubDate><guid>http://www.buildwithdc.co/guides/human-side-of-ai-transformation-guide/</guid><description>Every organization racing to adopt AI eventually runs into the same wall: the models keep improving, the tooling keeps maturing, and yet the transformation stalls at &amp;ldquo;incremental.&amp;rdquo; Teams get faster at the same work, not fundamentally different at it. The reason isn&amp;rsquo;t a missing feature in the tech stack — it&amp;rsquo;s that AI adoption is a technical problem, but AI transformation is a human one.
This guide brings together four articles that trace that human problem from its root cause down to the individual engineer&amp;rsquo;s daily judgment calls.</description></item><item><title>The AI-Driven Development Approach (AI-DLC): A Complete Guide</title><link>http://www.buildwithdc.co/guides/ai-driven-development-guide/</link><pubDate>Wed, 30 Jul 2025 07:35:49 +0800</pubDate><guid>http://www.buildwithdc.co/guides/ai-driven-development-guide/</guid><description>Generative AI has changed how software gets built, but most teams are still leaving the majority of its value on the table. The reason isn&amp;rsquo;t the model, the coding assistant, or the prompt template — it&amp;rsquo;s the underlying approach. Somewhere between &amp;ldquo;let the AI build everything&amp;rdquo; and &amp;ldquo;just use AI to autocomplete a function,&amp;rdquo; there&amp;rsquo;s a balanced, repeatable way of working that actually delivers a step-change in delivery speed without sacrificing quality or control.</description></item><item><title>Adaptive Systems Design: A Complete Guide</title><link>http://www.buildwithdc.co/guides/adaptive-systems-design-guide/</link><pubDate>Sun, 24 Nov 2024 10:23:30 +0800</pubDate><guid>http://www.buildwithdc.co/guides/adaptive-systems-design-guide/</guid><description>Every engineering team eventually runs into the same wall: the codebase that was fast to ship a year ago is now the thing slowing everyone down. Features that used to take days now take weeks. The team hasn&amp;rsquo;t gotten worse — the system has. The question is why this happens so predictably, across businesses, countries, and skill levels, and what can actually be done about it before the rewrite becomes the only option left.</description></item></channel></rss>