<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>The Blog on dxaws</title><link>https://dev.dxaws.com/blog/</link><description>Recent content in The Blog on dxaws</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026</copyright><lastBuildDate>Thu, 23 Apr 2026 18:48:59 +0000</lastBuildDate><atom:link href="https://dev.dxaws.com/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI (LLM) Situation</title><link>https://dev.dxaws.com/blog/2026-04-23-the-llm-situation/</link><pubDate>Thu, 23 Apr 2026 18:48:59 +0000</pubDate><guid>https://dev.dxaws.com/blog/2026-04-23-the-llm-situation/</guid><description>A real look at using LLMs in software engineering</description></item><item><title>The Registry Module Planning Session (part 2): Manager Interface Surface</title><link>https://dev.dxaws.com/blog/2026-04-16-registry-plan-manager-interface/</link><pubDate>Thu, 16 Apr 2026 21:51:10 +0000</pubDate><guid>https://dev.dxaws.com/blog/2026-04-16-registry-plan-manager-interface/</guid><description>&lt;h2 class="relative group"&gt;Introduction
 &lt;div id="introduction" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#introduction" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;In the previous post we defined the conceptual model for the registry.&lt;/p&gt;
&lt;p&gt;Now we begin defining the manager interface — the public surface through which other modules interact with the registry.&lt;/p&gt;

&lt;h2 class="relative group"&gt;Design Goals for the Manager
 &lt;div id="design-goals-for-the-manager" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#design-goals-for-the-manager" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;The registry will follow the same basic design principles as other modules in the &lt;code&gt;dxaws&lt;/code&gt; ecosystem. The &lt;code&gt;manager&lt;/code&gt; is not only the public interface to the module, but it also manages the work through the other parts of the module, namely the &lt;code&gt;planner&lt;/code&gt;, &lt;code&gt;executor&lt;/code&gt; and providers. We want to spend a bit of time thinking about the design of the interface to this module since it will be difficult to change down the road. Some other considerations for the module in general will include:&lt;/p&gt;</description></item><item><title>The Registry Module Planning Session (part 1)</title><link>https://dev.dxaws.com/blog/2026-04-16-registry-plan/</link><pubDate>Thu, 16 Apr 2026 13:22:10 +0000</pubDate><guid>https://dev.dxaws.com/blog/2026-04-16-registry-plan/</guid><description>&lt;h2 class="relative group"&gt;Introduction
 &lt;div id="introduction" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#introduction" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;Up to this point, we have focused on building primitive modules like DNS, ACM, S3, and CloudFront. As those pieces stabilize, the need for a registry becomes clearer: we need a consistent way to track what exists, where it lives, and who is responsible for it.&lt;/p&gt;
&lt;p&gt;Now that we have a design direction, we can jump right into the implementation planning. In this session, we want to start translating the design discussion into something we can actually build by:&lt;/p&gt;</description></item><item><title>The Dependency Gravity Model</title><link>https://dev.dxaws.com/blog/2026-04-09-dependency-gravity-model/</link><pubDate>Thu, 09 Apr 2026 19:54:37 +0000</pubDate><guid>https://dev.dxaws.com/blog/2026-04-09-dependency-gravity-model/</guid><description>&lt;h2 class="relative group"&gt;Introduction
 &lt;div id="introduction" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#introduction" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;This post is specifically about a planning technique I have used to prioritize my design work effort for many, many years. Defining priorities is one of those things that people seem to have a hard time with. In the interests of efficiency, we want to make sure that we are spending our time on the things that matter the most. I mean, it&amp;rsquo;s not all that hard to grab a bunch of pieces and glue them all together to build a system that works and claim victory. Unfortunately, one thing I learned very early on in my career is that building it is easy, the real work starts when people start to use it.&lt;/p&gt;</description></item><item><title>The Registry Module design session</title><link>https://dev.dxaws.com/blog/2026-04-09-the-registry-module/</link><pubDate>Thu, 09 Apr 2026 14:50:05 +0000</pubDate><guid>https://dev.dxaws.com/blog/2026-04-09-the-registry-module/</guid><description>&lt;h2 class="relative group"&gt;Introduction
 &lt;div id="introduction" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#introduction" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;At this point, we have a number of primitives that can be used to manage resources on AWS and a composition module that uses the primitives to build a website using Cloudfront/S3/ACM/Route53. It&amp;rsquo;s basically a single command like &amp;ldquo;I want a website called test1.dxaws.com in account #123 in region us-least-6&amp;rdquo; and away it goes. The whole process takes about five minutes, which seems pretty good, not great but there are some ways to optimize it even further by creating resource pools.&lt;/p&gt;</description></item></channel></rss>