
  <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>Sat, 06 Jun 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.rambling-me.com/tags/staff-engineer/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.rambling-me.com/blog/posts/technology/designing-systems/1-how-to-approach</guid>
    <title>Designing Systems: How to Approach a System Design</title>
    <link>https://www.rambling-me.com/blog/posts/technology/designing-systems/1-how-to-approach</link>
    <description>How a staff engineer actually approaches a system design in the wild. Framing the problem, separating requirements from constraints from tradeoffs, surfacing hidden assumptions, sketching before deciding, and treating the design as a communication artifact.</description>
    <pubDate>Sat, 06 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>NFR</category><category>tradeoffs</category><category>framing</category>
  </item>

  <item>
    <guid>https://www.rambling-me.com/blog/posts/technology/designing-systems/2-core-elements</guid>
    <title>Designing Systems: Core Elements</title>
    <link>https://www.rambling-me.com/blog/posts/technology/designing-systems/2-core-elements</link>
    <description>The five things every system design has to make concrete decisions about: data, state, control flow, failure, and observability. Each one is a hinge point where good and bad designs diverge.</description>
    <pubDate>Mon, 15 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>data</category><category>state</category><category>failure</category><category>observability</category>
  </item>

  <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>

  <item>
    <guid>https://www.rambling-me.com/blog/posts/technology/designing-systems/4-anti-patterns</guid>
    <title>Designing Systems: Anti-Patterns and What Experience Teaches</title>
    <link>https://www.rambling-me.com/blog/posts/technology/designing-systems/4-anti-patterns</link>
    <description>The failure modes that show up repeatedly across system designs, how to recognise them before they ship, what a good design actually feels like to work in, and a few habits that compound over a career.</description>
    <pubDate>Mon, 29 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>anti-patterns</category><category>failure-modes</category><category>habits</category>
  </item>

    </channel>
  </rss>
