<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>System_design on dxaws</title><link>https://dev.dxaws.com/tags/system_design/</link><description>Recent content in System_design on dxaws</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026</copyright><lastBuildDate>Thu, 09 Apr 2026 19:54:37 +0000</lastBuildDate><atom:link href="https://dev.dxaws.com/tags/system_design/index.xml" rel="self" type="application/rss+xml"/><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></channel></rss>