<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Future of Engineering on Derick Chen</title><link>http://www.buildwithdc.co/tags/future-of-engineering/</link><description>Recent content in Future of Engineering on Derick Chen</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 01 Apr 2026 17:30:00 +0800</lastBuildDate><atom:link href="http://www.buildwithdc.co/tags/future-of-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>The Future of Software Engineering: From Code Writers to AI Workflow Conductors</title><link>http://www.buildwithdc.co/posts/the-future-of-software-engineering-from-code-writers-to-ai-orchestrators/</link><pubDate>Wed, 01 Apr 2026 17:30:00 +0800</pubDate><guid>http://www.buildwithdc.co/posts/the-future-of-software-engineering-from-code-writers-to-ai-orchestrators/</guid><description>Engineering was never just about writing code. It was always about building things that work — and knowing how to fix them when they don&amp;rsquo;t.
There&amp;rsquo;s a debate happening in engineering circles right now, and it mostly misses the point. Some argue that AI will replace software engineers. Others argue that engineers will always be needed because AI can&amp;rsquo;t &amp;ldquo;truly&amp;rdquo; reason. Both sides are arguing about the wrong thing.
The more interesting question isn&amp;rsquo;t whether engineers will be replaced.</description></item></channel></rss>