<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Dependencies on Steffen Hoppe – Infrastructure Reality &amp; Insight</title>
    <link>https://www.sh-soft.de/tags/dependencies/</link>
    <description>Recent content in Dependencies on Steffen Hoppe – Infrastructure Reality &amp; Insight</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 26 Jun 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.sh-soft.de/tags/dependencies/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Sales System Project: Automation Boundaries</title>
      <link>https://www.sh-soft.de/posts/sales-system/automation-boundaries/</link>
      <pubDate>Thu, 26 Jun 2025 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/posts/sales-system/automation-boundaries/</guid>
      <description>🚧 Automation Boundaries Link to heading Summary: Automation helped us move faster, reduce errors, and scale operations.&#xA;But it didn’t solve everything — especially when our systems had to interact with others.&#xA;Where the Boundaries Appeared Link to heading Active Directory and DNS: We didn’t own it. Scripted group changes or DNS edits weren’t possible without external coordination. Firewall Rules and Load Balancers: Managed by a different team. Automation stopped at the request ticket.</description>
    </item>
  </channel>
</rss>
