<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Architectural Taste on Derick Chen</title><link>http://www.buildwithdc.co/tags/architectural-taste/</link><description>Recent content in Architectural Taste 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/tags/architectural-taste/index.xml" rel="self" type="application/rss+xml"/><item><title>The Calibrated Engineer: Timeless Principles for the AI-Native Era</title><link>http://www.buildwithdc.co/posts/the-calibrated-engineer-timeless-principles-for-the-ai-native-era/</link><pubDate>Wed, 10 Jun 2026 12:00:00 +0800</pubDate><guid>http://www.buildwithdc.co/posts/the-calibrated-engineer-timeless-principles-for-the-ai-native-era/</guid><description>Why judgment outlasts generation when code becomes a commodity.
I&amp;rsquo;ve observed a dangerous conflation happening across development teams right now. As AI tools rapidly accelerate our output, we are collectively making the mistake of treating &amp;ldquo;engineering&amp;rdquo; and &amp;ldquo;typing code&amp;rdquo; as the exact same discipline.
They aren&amp;rsquo;t.
To understand what makes a truly great software builder today, we have to aggressively decouple the two. The modern, AI-augmented landscape forces us to distinguish between roles that historically blurred together behind a single job title:</description></item></channel></rss>