
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Rambling Me</title>
      <link>https://www.rambling-me.com/blog</link>
      <description>A blog to reflect my thoughts, learnings, and observations</description>
      <language>en-us</language>
      <managingEditor>me@rambling-me.com (Dopeking)</managingEditor>
      <webMaster>me@rambling-me.com (Dopeking)</webMaster>
      <lastBuildDate>Mon, 22 Jun 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.rambling-me.com/tags/evolution/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.rambling-me.com/blog/posts/technology/designing-systems/3-structuring-for-change</guid>
    <title>Designing Systems: Structuring for Change</title>
    <link>https://www.rambling-me.com/blog/posts/technology/designing-systems/3-structuring-for-change</link>
    <description>A system survives or fails by how it handles change. Boundaries between components, contracts at the seams, the cost of evolving a live system, and the ownership map that determines who is allowed to change what.</description>
    <pubDate>Mon, 22 Jun 2026 00:00:00 GMT</pubDate>
    <author>me@rambling-me.com (Dopeking)</author>
    <category>technology</category><category>system-design</category><category>designing-systems</category><category>practitioner</category><category>staff-engineer</category><category>boundaries</category><category>contracts</category><category>evolution</category><category>ownership</category>
  </item>

    </channel>
  </rss>
