<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Blog on Steffen Hoppe – Infrastructure Reality &amp; Insight</title>
    <link>https://www.sh-soft.de/posts/</link>
    <description>Recent content in Blog on Steffen Hoppe – Infrastructure Reality &amp; Insight</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 04 Feb 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.sh-soft.de/posts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Infrastructure Reality — A Series About the Hidden Mechanics of Modern Systems</title>
      <link>https://www.sh-soft.de/posts/infra-reality/infra-reality-roadmap/</link>
      <pubDate>Wed, 19 Nov 2025 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/posts/infra-reality/infra-reality-roadmap/</guid>
      <description>Infrastructure Reality — A Series About the Hidden Mechanics of Modern Systems Link to heading Modern infrastructure does not behave the way teams assume it does.&#xA;Systems drift, defaults override intentions, configuration layers interact in ways nobody fully sees, and documentation lags behind the moment it is written. Everyone believes they “know” their environment — until something behaves differently than expected.&#xA;This gap between assumed truth and technical reality is one of the biggest hidden problems in enterprise IT today.</description>
    </item>
    <item>
      <title>The Sales System Project – Overview</title>
      <link>https://www.sh-soft.de/posts/sales-system/sales-system-overview/</link>
      <pubDate>Thu, 29 May 2025 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/posts/sales-system/sales-system-overview/</guid>
      <description>📦 The Sales System Project – Overview Link to heading This series dives into a complex, long-running engagement centered on a fragile in-house sales system.&#xA;The customer hosted 1,000+ Windows systems across development, test, and production stages.&#xA;What began as firefighting evolved into automation, observability, and ultimately organizational change.&#xA;The Journey begins Link to heading About 14 years ago, I took over responsibility for a single, large, in-house-developed sales system.</description>
    </item>
    <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>
    <item>
      <title>Sales System Project: Organizational Change</title>
      <link>https://www.sh-soft.de/posts/sales-system/organizational-change/</link>
      <pubDate>Thu, 19 Jun 2025 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/posts/sales-system/organizational-change/</guid>
      <description>🏢 Organizational Change Link to heading Hey, what&amp;rsquo;s happening here? Link to heading Organizations constantly update their processes.&#xA;Tools are replaced. Responsibilities shift.&#xA;Sometimes it&amp;rsquo;s about security. Sometimes it&amp;rsquo;s compliance. Sometimes it&amp;rsquo;s mergers.&#xA;But most of the time — it ends in frustration.&#xA;Why is that? Link to heading There are many reasons this kind of change leads to problems:&#xA;Reasons for the changes are not clearly communicated New processes don&amp;rsquo;t work — or work poorly — out of the box People fear the unknown What to do?</description>
    </item>
    <item>
      <title>Creating PowerShell Modules: Structure, Packaging, Testing, and Code Signing</title>
      <link>https://www.sh-soft.de/posts/powershell/creating-powershell-modules/</link>
      <pubDate>Thu, 19 Jun 2025 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/posts/powershell/creating-powershell-modules/</guid>
      <description>PowerShell modules provide a clean, powerful way to package, share, and maintain automation code. Instead of scattered scripts, modules help you organize your functions, enforce consistency, and deliver reliable tools to colleagues, teams, or external users.&#xA;Why write modules?&#xA;📦 Reusability: Group related functions together for easy reuse across projects. ⚙ Maintainability: Simplify updates, debugging, and version control. 🤝 Collaboration: Provide a clear API surface for team members or customers. 🚀 Distribution: Make your code installable via PowerShell Gallery, NuGet feeds, or internal repositories.</description>
    </item>
    <item>
      <title>Sales System Project: The key to success is Constant Evolution</title>
      <link>https://www.sh-soft.de/posts/sales-system/constant-evolution/</link>
      <pubDate>Thu, 12 Jun 2025 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/posts/sales-system/constant-evolution/</guid>
      <description>🔄 The Key to Success is Constant Evolution Link to heading The fixes and insights from our firefighting phase weren’t the end — they were just the beginning.&#xA;We quickly realized that stabilizing a system is one thing, but keeping it healthy, fast, and maintainable over the long term requires ongoing, strategic evolution.&#xA;So we created a plan on what to enhance and just started working. And we are still at it.</description>
    </item>
    <item>
      <title>Sales System Project: First Firefights</title>
      <link>https://www.sh-soft.de/posts/sales-system/first-firefights/</link>
      <pubDate>Thu, 05 Jun 2025 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/posts/sales-system/first-firefights/</guid>
      <description>🔥 First Firefights Link to heading In the early days, most of our effort went into understanding where things failed.&#xA;The system would break under pressure, produce unclear error messages, or behave unreliably depending on deployment timing.&#xA;We had no telemetry. No usable monitoring. Bug reports were anecdotal.&#xA;This forced us into manual observation and creative debugging — and pushed us to establish a more structured approach to system setup and error diagnostics.</description>
    </item>
    <item>
      <title>Sales System Project: Setup and Problems</title>
      <link>https://www.sh-soft.de/posts/sales-system/setup-problems/</link>
      <pubDate>Thu, 29 May 2025 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/posts/sales-system/setup-problems/</guid>
      <description>🏗️ Setup and Problems Link to heading Setup Link to heading Customer Landscape:&#xA;Initially ~200 Windows servers, later scaled to over 1,000 across development, test, and production as new services were added and integrated into our automation Primarily Windows-based infrastructure: IIS, MSMQ, MSSQL, and some JBoss AD integrated authentication via NTLM and Kerberos, sometimes Basic Auth, host backend integration via IBM MQ Business-critical data processed via mainframe interfaces Different teams have control over: Active Directory: DNS / Users / Groups Firewall and Security Infrastructure Reverse Proxies Virtualization platform PKI Internal traffic often unencrypted due to lack of automated PKI or cert lifecycle Problems Link to heading Initial Challenges:</description>
    </item>
    <item>
      <title>The Path Toward Infrastructure Truth</title>
      <link>https://www.sh-soft.de/posts/infra-reality/infrastructure-truth-path/</link>
      <pubDate>Wed, 04 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/posts/infra-reality/infrastructure-truth-path/</guid>
      <description>Placeholder content.&#xA;This post will outline the foundational steps toward understanding real system behavior.</description>
    </item>
    <item>
      <title>Why Rule Engines Fail</title>
      <link>https://www.sh-soft.de/posts/infra-reality/rule-engines-fail/</link>
      <pubDate>Wed, 28 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/posts/infra-reality/rule-engines-fail/</guid>
      <description>Placeholder content.&#xA;This post will explain why rule engines explode in complexity and cannot control real-world systems.</description>
    </item>
    <item>
      <title>Telemetry-First Infrastructure</title>
      <link>https://www.sh-soft.de/posts/infra-reality/telemetry-first/</link>
      <pubDate>Wed, 21 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/posts/infra-reality/telemetry-first/</guid>
      <description>Placeholder content.&#xA;This post will explore why telemetry must precede decision-making and automation.</description>
    </item>
    <item>
      <title>The CMDB Reality Gap</title>
      <link>https://www.sh-soft.de/posts/infra-reality/cmdb-reality-gap/</link>
      <pubDate>Wed, 14 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/posts/infra-reality/cmdb-reality-gap/</guid>
      <description>Placeholder content.&#xA;This post will analyze why CMDBs never match the real environment.</description>
    </item>
    <item>
      <title>Why Dev, Test and Prod Are Never Identical</title>
      <link>https://www.sh-soft.de/posts/infra-reality/envs-never-identical/</link>
      <pubDate>Wed, 07 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/posts/infra-reality/envs-never-identical/</guid>
      <description>Placeholder content.&#xA;This post will explain why environments drift the moment they exist.</description>
    </item>
    <item>
      <title>Effective Configuration — The Only Truth That Matters</title>
      <link>https://www.sh-soft.de/posts/infra-reality/effective-config/</link>
      <pubDate>Wed, 31 Dec 2025 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/posts/infra-reality/effective-config/</guid>
      <description>Placeholder content.&#xA;This post will describe effective configuration and why it must be the primary decision basis.</description>
    </item>
    <item>
      <title>Configuration Layering</title>
      <link>https://www.sh-soft.de/posts/infra-reality/config-layering/</link>
      <pubDate>Wed, 24 Dec 2025 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/posts/infra-reality/config-layering/</guid>
      <description>Placeholder content.&#xA;This post will explain layering, precedence and inheritance — the true source of config complexity.</description>
    </item>
    <item>
      <title>The Hidden World of Runtime Defaults — The Configuration Layer Nobody Sees</title>
      <link>https://www.sh-soft.de/posts/infra-reality/defaults-hidden-world/</link>
      <pubDate>Wed, 17 Dec 2025 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/posts/infra-reality/defaults-hidden-world/</guid>
      <description>Most teams underestimate the influence of defaults.&#xA;They focus on configuration files, parameters, and declarative settings – the parts of a system they can see and control. But these represent only a small fraction of the actual configuration that determines system behaviour.&#xA;The rest comes from runtime defaults: values embedded in libraries, subsystems, frameworks, OS layers and fallback mechanisms. They change silently, vary by version, and can override explicit configuration without leaving any trace in repos or documentation.</description>
    </item>
    <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>
    <item>
      <title>The Documentation Illusion — Why Technical Truth Rarely Lives in Documents</title>
      <link>https://www.sh-soft.de/posts/infra-reality/documentation-illusion/</link>
      <pubDate>Wed, 03 Dec 2025 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/posts/infra-reality/documentation-illusion/</guid>
      <description>Organizations treat documentation as if it were the anchor of truth in their infrastructure.&#xA;It promises structure, continuity, onboarding, governance and transparency.&#xA;But documentation rarely fulfills that promise.&#xA;Not because people are lazy, but because the system it tries to describe — and the organization around it — move faster than any document can keep up with.&#xA;This article explores why documentation consistently fails to represent technical truth, why this is not a problem you can fix with discipline, and why the illusion persists nonetheless.</description>
    </item>
    <item>
      <title>Systems Never Behave As Intended</title>
      <link>https://www.sh-soft.de/posts/infra-reality/systems-never-behave/</link>
      <pubDate>Wed, 26 Nov 2025 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/posts/infra-reality/systems-never-behave/</guid>
      <description>Most systems do not behave according to their design documentation, their architecture diagrams or the expectations expressed during discussions.&#xA;They behave according to the sum of their runtime conditions — conditions that are rarely fully visible, rarely fully controlled, and often only understood after something goes wrong.&#xA;This gap between intended behaviour and actual behaviour is one of the core reasons why modern systems surprise their operators, drift over time and resist prediction.</description>
    </item>
    <item>
      <title>The Pain Landscape of Modern Infrastructure</title>
      <link>https://www.sh-soft.de/posts/infra-reality/pain-landscape/</link>
      <pubDate>Wed, 19 Nov 2025 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/posts/infra-reality/pain-landscape/</guid>
      <description>Modern IT landscapes do not break because people are careless.&#xA;They break because the systems they operate grow in complexity faster than teams can understand them.&#xA;Over the years, across insurance, finance, logistics and public-sector environments, the same patterns appear again and again. Different organizations, different architectures, different tools — and yet the pain is nearly identical.&#xA;This article outlines the most common pain points that shape the daily reality of operations teams.</description>
    </item>
    <item>
      <title>PowerShell - Logging</title>
      <link>https://www.sh-soft.de/posts/powershell/02.02-on-logging/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/posts/powershell/02.02-on-logging/</guid>
      <description>PowerShell Logging Link to heading Something each script and application should have&#xA;Every PowerShell script—whether it&amp;rsquo;s a one-liner or a full-blown module—benefits from logging. It&amp;rsquo;s not just about showing messages on the screen. Logging is essential to:&#xA;✅ Show status / give feedback to the user ✅ Keep logs for audits ✅ Trace errors effectively in production Pitfalls Link to heading ❌ Console-only output Link to heading The default PowerShell logging commands (Write-Host, Write-Verbose, Write-Debug) only display information at runtime.</description>
    </item>
  </channel>
</rss>
