<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>schristoph.online</title><link>https://schristoph.online/tags/awsarchitecture/</link><description>Personal homepage and blog of Stefan Christoph</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>Stefan Christoph. All rights reserved.</copyright><lastBuildDate>Mon, 13 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://schristoph.online/tags/awsarchitecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Laws &amp; Disorder #1 — Conway's Law: Your Org Chart Is Your Real Architecture (and AI Is Redrawing Both)</title><link>https://schristoph.online/blog/conways-law-your-org-is-your-architecture/?utm=rss-feed</link><pubDate>Mon, 13 Jul 2026 00:00:00 +0000</pubDate><guid>https://schristoph.online/blog/conways-law-your-org-is-your-architecture/</guid><description>&lt;p>🎬 Also available as a &lt;a href="https://youtu.be/RViNNzcw1jc">blog walkthrough video&lt;/a> — a short narrated screencast of this post.&lt;/p>
&lt;div class="tldr" data-pagefind-weight="5" data-pagefind-meta="tldr" style="display:block;font-size:.875em;margin:2rem 0;border-left:4px solid #ccc;padding-left:1rem;line-height:1.5;">&lt;strong>TL;DR:&lt;/strong> Conway&amp;rsquo;s Law says a system&amp;rsquo;s structure ends up mirroring the communication structure of the organization that built it. On AWS your service and account boundaries drift toward your team boundaries whether you planned it or not, so the Inverse Conway Maneuver is real power: shape the teams first to get the architecture you want. In my own years holding an architecture together across many services and many teams, the existing team structure was almost always the hard wall I hit when I tried to change the overall design. The new twist, as of 2026: AI coding assistants lower the coordination cost between teams, the exact cost Conway&amp;rsquo;s Law runs on, and fleets of AI agents are starting to show up on the org chart too. Whether that loosens the org-to-architecture mapping or just replicates the old one faster is the open question worth sitting with.&lt;/div>
&lt;p>&lt;em>This is the first post in &amp;ldquo;Laws &amp;amp; Disorder,&amp;rdquo; a short series where I take a software-engineering &amp;ldquo;law&amp;rdquo; we all half-quote, admit it&amp;rsquo;s a heuristic and not a law of physics, and ask what it means for building on the cloud in the age of AI. First up: the one that keeps quietly winning arguments in architecture reviews.&lt;/em>&lt;/p></description></item></channel></rss>