<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Architecture on Blog</title><link>https://blog.rickwaterman.com/tags/architecture/</link><description>Recent content in Architecture on Blog</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 14 May 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.rickwaterman.com/tags/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>If You Are Not Part of the Implementation, You Are Part of the Problem</title><link>https://blog.rickwaterman.com/posts/if-you-are-not-part-of-the-implementation/</link><pubDate>Tue, 14 May 2024 00:00:00 +0000</pubDate><guid>https://blog.rickwaterman.com/posts/if-you-are-not-part-of-the-implementation/</guid><description>An architect who does not ship code has no feedback loop, and an architecture with no feedback loop is a guess with a diagram. Own a real piece of the build — the hard module, the infrastructure as code, the review queue — or accept that the team will route around you.</description></item><item><title>Boring Managed Services Win</title><link>https://blog.rickwaterman.com/posts/boring-managed-services-win/</link><pubDate>Mon, 04 Dec 2023 00:00:00 +0000</pubDate><guid>https://blog.rickwaterman.com/posts/boring-managed-services-win/</guid><description>Every queue, scheduler, or database you run yourself spends an innovation token on something your customers will never notice. Managed AWS services are boring in the best sense: their failure modes are documented, their metrics ship by default, and the toil they remove is the toil nobody measures.</description></item></channel></rss>