<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Documentation on Steffen Hoppe – Infrastructure Reality &amp; Insight</title>
    <link>https://www.sh-soft.de/tags/documentation/</link>
    <description>Recent content in Documentation on Steffen Hoppe – Infrastructure Reality &amp; Insight</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Jan 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.sh-soft.de/tags/documentation/index.xml" rel="self" type="application/rss+xml" />
    <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>Documentation is useful — but only close to the work</title>
      <link>https://www.sh-soft.de/pings/014-documentation-usefulness/</link>
      <pubDate>Fri, 02 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/pings/014-documentation-usefulness/</guid>
      <description>Documentation becomes effective when it is written by the people who do the work, for the people who do the work.&#xA;It helps with repeatability, clarity and avoiding mistakes.&#xA;But this value rarely scales.&#xA;Local documentation reflects reality.&#xA;Organizational documentation reflects narrative.</description>
    </item>
    <item>
      <title>Documentation creates the illusion of control</title>
      <link>https://www.sh-soft.de/pings/011-documentation-creates-illusion-of-control/</link>
      <pubDate>Tue, 23 Dec 2025 00:00:00 +0000</pubDate>
      <guid>https://www.sh-soft.de/pings/011-documentation-creates-illusion-of-control/</guid>
      <description>Many teams produce documentation to satisfy organizational expectations — to show that systems are structured, understandable and under control.&#xA;But if documentation truly reflected reality, people would say:&#xA;“Read the documentation first.”&#xA;They rarely do.&#xA;Instead, they tell you who to ask.&#xA;Documentation often describes how systems should be, not how they actually work.</description>
    </item>
  </channel>
</rss>
