<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Technical Debt on Research Logs</title><link>https://williamresearch.com/tags/technical-debt/</link><description>Recent content in Technical Debt on Research Logs</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 31 Aug 2026 23:11:12 +0700</lastBuildDate><atom:link href="https://williamresearch.com/tags/technical-debt/index.xml" rel="self" type="application/rss+xml"/><item><title>🧭 Architecture DNA Compass: Read Systems Beyond Pattern Labels</title><link>https://williamresearch.com/posts/architecture-dna-compass/</link><pubDate>Mon, 31 Aug 2026 23:11:12 +0700</pubDate><guid>https://williamresearch.com/posts/architecture-dna-compass/</guid><description>&lt;h2 id="1-the-hook-an-architecture-is-not-a-product-label"&gt;1. The Hook: an architecture is not a product label&lt;/h2&gt;
&lt;p&gt;Ask a team what architecture it runs and the answer often sounds like a technology catalog: microservices, event-driven, CQRS, Kubernetes, perhaps hexagonal architecture for good measure. The labels may all be true—and still explain surprisingly little.&lt;/p&gt;
&lt;p&gt;A real system can be a modular monolith at the deployment boundary, hexagonal inside selected modules, event-driven across domains, and CQRS only where read and write pressures diverge. These terms do not compete on one axis. They describe different forces.&lt;/p&gt;</description></item></channel></rss>