<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Drift on Steffen Hoppe – Infrastructure Reality &amp; Insight</title>
    <link>https://www.sh-soft.de/categories/drift/</link>
    <description>Recent content in Drift on Steffen Hoppe – Infrastructure Reality &amp; Insight</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 10 Dec 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.sh-soft.de/categories/drift/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Understanding Drift — Why Systems Move Away From Their Intended State</title>
      <link>https://www.sh-soft.de/posts/infra-reality/understanding-drift/</link>
      <pubDate>Wed, 10 Dec 2025 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/posts/infra-reality/understanding-drift/</guid>
      <description>Most organizations acknowledge the existence of drift but treat it as an operational nuisance — something that happens occasionally due to human error or missing documentation.&#xA;In reality, drift is not an exception.&#xA;It is the natural state of long-lived systems.&#xA;Drift is what happens when a system evolves faster than its declared intent, its documentation and its automation can keep up. And it happens everywhere, across all layers — configuration, code, defaults, deployments, environments, processes and organizational structures.</description>
    </item>
  </channel>
</rss>
